Arx Libertatis Bug Tracker ~ [CLOSED] #274 - [4B61E591] arx.exe!D3D9VertexBuffer<SMY

Arx Libertatis Bug Tracker

CLOSED Crash report #274 - [4B61E591] arx.exe!D3D9VertexBuffer<SMY_VERTEX>::lock() d3d9vertexbuffer.h(136)

Posted Jun 13, 2012 - updated Jul 03, 2012 Shortlink: http://arx.vg/274

Votes

This issue has been closed with status "Fixed" and resolution "RESOLVED".

Issue details

Type of issue

Crash report Unknown issue type
Status

Fixed

Status not determined
Assigned to

Not assigned to anyone
Progress
Type of bug

Not triaged
Likelihood

Not triaged
Effect

Not triaged
Posted by

CrashBot

CrashBot
Offline

This user was last seen online at Mar 25, 2025 - 14:18

Show user details

Close this menu
Owned by

Not owned by anyone
Estimated time

No time Not estimated
Time spent

No time No time spent
Category

Not determined
Resolution

RESOLVED Not determined
Priority

Not determined
Reproducability

Not determined
Severity

Not determined
Targetted for

Not determined
OS

WindowsNot determined
Architecture

amd64Not determined
Fixed in

Arx Libertatis 1.0.3Not determined

Issue description

Illegal storage access

Callstack:

  arx.exe!D3D9VertexBuffer<SMY_VERTEX>::lock()  d3d9vertexbuffer.h(136) 
  arx.exe!ComputePortalVertexBuffer()  mesh.cpp(4299) 
  arx.exe!ArxGame::InitDeviceObjects()  arxgame.cpp(2293) 
  arx.exe!ArxGame::onRendererInit()  arxgame.cpp(2337) 
  arx.exe!D3D9Window::restoreObjects()  d3d9window.cpp(337) 
  arx.exe!D3D9Window::setWindowSize()  d3d9window.cpp(329) 
  arx.exe!ArxGame::setFullscreen()  arxgame.cpp(274) 
  arx.exe!ArxGame::Render()  arxgame.cpp(936) 
  arx.exe!ArxGame::Run()  arxgame.cpp(564) 
  arx.exe!runGame()  core.cpp(842) 
  arx.exe!WinMain()  core.cpp(875) 
  arx.exe!__tmainCRTStartup()  crtexe.c(547) 
  kernel32.dll!BaseThreadInitThunk() 
  ntdll.dll!RtlUserThreadStart()

Registers:

  RAX:0000000000001000  RBX:0000000000000000  RCX:0000000028F46540  RDX:0000000000000000  RSI:0000000000000000  RDI:0000000000000000
  CS:RIP:0033:76E1C521
  SS:RSP:002B:00000000009BFF90  RBP:0000000000000000
  DS:002B  ES:002B  FS:0053  GS:002B
  Flags:00010246

Steps to reproduce this issue

ALT TAB to the desktop and then back again but the only showed a black screen so I did a few more ALT TAB and trying to get back ingame. I was on the menu (ESC) while doing this.

Show system-generated comments

Comment posted on behalf of

CrashBot

Jun 13, 19:19

The issue was updated with the following change(s):

The custom field OS has been updated to Windows.
The custom field Architecture has been updated to amd64.

Comment posted by

CrashBot

Jun 13, 19:19

A file was uploaded. arx.log

This comment was attached:

arxcrash-3524-3020082937

Comment posted by

CrashBot

Jun 13, 19:19

A file was uploaded. cfg.ini

This comment was attached:

arxcrash-3524-3020082937

Comment posted by

CrashBot

Jun 13, 19:20

A file was uploaded. crash.dmp

This comment was attached:

arxcrash-3524-3020082937

Comment posted by

CrashBot

Jun 13, 19:20

A file was uploaded. crash.xml

This comment was attached:

arxcrash-3524-3020082937

Comment posted on behalf of

Daniel Scharrer

Jun 16, 01:27

The issue was updated with the following change(s):

The milestone has been updated, from Not determined to 1.0.3.

Comment posted on behalf of

Daniel Scharrer

Jun 22, 20:25

The issue was updated with the following change(s):

The milestone has been updated, from Not determined to 1.0.3.

Comment posted on behalf of

Daniel Scharrer

Jun 22, 21:09

The issue was updated with the following change(s):

The milestone has been updated, from Not determined to 1.0.3.

Comment posted on behalf of

Guest user

Jul 03, 03:22

This issue has been updated with the latest changes from the code repository.

Improved handling of D3D9 lost device state.
 
Previously, I relied on the fact that most calls to D3D should succeed even when a device is lost:
http://msdn.microsoft.com/en-us/library/windows/desktop/bb174714(v=vs.85).aspx
 
That still led to a few corner cases that were not handled properly... Now the game will be stuck in D3D9Window::tick() in case of a lost device, but it will keep on processing messages. This is much safer.
 
Fixes bug #274
Fixes bug #314

#10

Comment posted on behalf of

SebastienLussier

Jul 03, 03:23

The issue was updated with the following change(s):

This issue has been closed
The status has been updated, from New to Fixed.
The resolution has been updated, from Not determined to RESOLVED.
This issue's progression has been updated to 100 percent completed.

#11

Comment posted on behalf of

Daniel Scharrer

Jul 03, 04:51

The issue was updated with the following change(s):

The status has been updated, from Fixed to New.
This issue has been reopened
The resolution has been updated, from RESOLVED to Not determined.
This issue's progression has been updated to 0 percent completed.

#12

Comment posted on behalf of

Daniel Scharrer

Jul 03, 04:52

The issue was updated with the following change(s):

The custom field Fixed in has been updated, from Unknown to Arx Libertatis 1.0.3.

#13

Comment posted on behalf of

Daniel Scharrer

Jul 03, 04:52

The issue was updated with the following change(s):

This issue has been closed
The status has been updated, from New to Fixed.
The resolution has been updated, from Not determined to RESOLVED.
This issue's progression has been updated to 100 percent completed.

* Username
* Display name
The "display name" is the name shown to others
Real name
* E-mail address
* Confirm e-mail

Welcome to The Bug Genie

Really delete this comment?

Really delete this comment?

Really delete this comment?

Really delete this comment?

Really delete this comment?

Really delete this comment?

Really delete this comment?

Really delete this comment?

Really delete this comment?

Really delete this comment?

Really delete this comment?

Really delete this comment?

Really delete this comment?

Username
Password