#1006 closed defect (worksforme)
glDrawElements crash in CPatchRData::RenderBases
Reported by: | Erik Johansson | Owned by: | |
---|---|---|---|
Priority: | Should Have | Milestone: | |
Component: | Core engine | Keywords: | crash |
Cc: | Patch: |
Description
Much to our regret we must report the program has encountered an error. Please let us know at http://trac.wildfiregames.com/ and attach the crashlog.txt and crashlog.dmp files. Details: unhandled exception (Access violation reading 0x2EC010A4) Location: unknown:0 (?) Call stack: (error while dumping stack: No stack frames found) errno = 0 (No error reported here) OS error = 0 (no error code was set)
After playing just say a minute or so at most the above did appear in an error dialog. Using the latest autobuild (from 10409) and SVN version 10427, but according to Ben it's an error in the terrain rendering code so that shouldn't be the problem.
Attachments (2)
Change History (11)
by , 13 years ago
Attachment: | crashlog.dmp added |
---|
by , 13 years ago
Attachment: | crashlog.txt added |
---|
comment:1 by , 13 years ago
comment:2 by , 13 years ago
Given right to left param pushing order, it looks like the rightmost one to glDrawElements (indices=0x2ec010b4) is bogus. Although this value depends on registers still being valid, I assume so because it is close to the value reported in the exception.
comment:3 by , 12 years ago
Summary: | Crash during game → glDrawElements crash in CPatchRData::RenderBases |
---|
comment:8 by , 11 years ago
Resolution: | → worksforme |
---|---|
Status: | new → closed |
comment:9 by , 11 years ago
Milestone: | Backlog |
---|
Note:
See TracTickets
for help on using tickets.
I've had this problem on a Windows XP laptop with Intel graphics, usually when moving the camera around. I suppose if it's a driver issue, there is an error condition we should be checking to prevent a crash (since it's an memory access violation).