Arx Libertatis Bug Tracker ~ [CLOSED] #314 - [57F42282] arx.exe!D3D9VertexBuffer<TexturedVertex>::lock() d3d9vertexbuffer.h(136)

Arx Libertatis Bug Tracker

CLOSED Crash report #314 - [57F42282] arx.exe!D3D9VertexBuffer<TexturedVertex>::lock() d3d9vertexbuffer.h(136)

Posted Jun 30, 2012 - updated Jul 03, 2012 Shortlink: http://arx.vg/314

Votes

This issue is a duplicate of issue #274 - "[4B61E591] arx.exe!D3D9VertexBuffer<SMY_VERTEX>::lock() d3d9vertexbuffer.h(136) "

This issue has been closed with status "Not a bug" and resolution "DUPLICATE".

Issue details

Type of issue

Crash report Unknown issue type
Status

Not a bug

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 Apr 24, 2024 - 16:45

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

DUPLICATE Not determined
Priority

Not determined
Reproducability

Not determined
Severity

Not determined
Targetted for

Not determined
OS

WindowsNot determined
Architecture

amd64Not determined
Fixed in

Not determined

Issue description

Illegal storage access

Callstack:

  arx.exe!D3D9VertexBuffer<TexturedVertex>::lock()  d3d9vertexbuffer.h(136) 
  arx.exe!D3D9VertexBuffer<TexturedVertex>::setData()  d3d9vertexbuffer.h(126) 
  arx.exe!EERIEDrawBitmap2()  draw.cpp(937) 
  arx.exe!ARX_Menu_Render()  menu.cpp(575) 
  arx.exe!ArxGame::Render()  arxgame.cpp(934) 
  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:0000000000002000  RBX:0000000000000000  RCX:000000006165685F  RDX:000000004035DAB8  RSI:0000000000000000  RDI:0000000000000000
  CS:RIP:0033:7706C521
  SS:RSP:002B:00000000009BFF90  RBP:0000000000000000
  DS:002B  ES:002B  FS:0053  GS:002B
  Flags:00010217

Steps to reproduce this issue

Trying to play in windowed mode, alt tab not working, so I clicked on the Show Desktop button for Windows 7. Then this.

Show system-generated comments

Comment posted on behalf of

CrashBot

Jun 30, 16:12

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 30, 16:12

A file was uploaded. arx.log

This comment was attached:

arxcrash-1192-3430550874

Comment posted by

CrashBot

Jun 30, 16:12

A file was uploaded. cfg.ini

This comment was attached:

arxcrash-1192-3430550874

Comment posted by

CrashBot

Jun 30, 16:12

A file was uploaded. crash.dmp

This comment was attached:

arxcrash-1192-3430550874

Comment posted by

CrashBot

Jun 30, 16:12

A file was uploaded. crash.xml

This comment was attached:

arxcrash-1192-3430550874

Comment posted by

Daniel Scharrer

Jun 30, 17:22

Probably a duplicate of Crash report 274 - [4B61E591] arx.exe!D3D9VertexBuffer<SMY_VERTEX>::lock() d3d9vertexbuffer.h(136)

Comment posted on behalf of

Daniel Scharrer

Jun 30, 17:22

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

Comment posted on behalf of

SebastienLussier

Jul 03, 03:24

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.

#10

Comment posted on behalf of

Daniel Scharrer

Jul 03, 04:54

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.

#11

Comment posted on behalf of

Daniel Scharrer

Jul 03, 04:54

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

The status has been updated, from New to Not a bug.
This issue has been closed
The resolution has been updated, from Not determined to DUPLICATE.

* 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?

Username
Password