View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0002719 | FSSCP | OpenGL | public | 2012-10-16 21:38 | 2012-11-18 18:41 |
Reporter | Admiral MS | Assigned To | Valathil | ||
Priority | normal | Severity | crash | Reproducibility | always |
Status | resolved | Resolution | fixed | ||
OS | Windows | ||||
Target Version | 3.6.16 | ||||
Summary | 0002719: Lab crash after switchting from ship debris to another ship | ||||
Description | The Lab crashes with a memory access violation (windows is closing the application when not using MSVC for debugging) after switching from ship debris to another ship (not relevant if it's to debris or to normal LODs). It seems that the crash was introduced in revision 9101 (was unable to reproduce it with 9100) and happens in release and debug builds. Tested it without any mods or mediavps active. | ||||
Steps To Reproduce | 1. Open the F3 Lab and the ships menu 2. Select debris of any ship 3. Select another ship 4. repeat 2. and 3. until it crashes Usually the crash happens during the first or second switch but sometimes it takes more. | ||||
Additional Information | Call stack: http://pastebin.com/vFehiWSc | ||||
Tags | No tags attached. | ||||
|
Some additions: Debug Log: http://pastebin.com/QVV7hS0b And crash doesn't happen when using intel graphics instead of the nvidia graphics card. |
|
It would be good if you (or anyone else who can repro this with a debugger attached) could analyze the state of the program when this crash is hit; especially the state of the pointers passed to opengl during opengl_draw_coloured_quad. |
|
I can't reproduce this crash. Has this been fixed in another commit I wonder? Have you tried testing this on the latest nightlies? |
|
It's still present in the latest nightlies. I also tested it on two other computers where the same happens (both have a nivida card). |
|
I can also reproduce this crash on the latest trunk builds. (Build 9340) |
|
Anyone on an AMD card reproduce this crash? |
|
I'm on a AMD card and I can't reproduce this crash using retail data. |
|
AMD card here as well and can't reproduce. |
|
Fixed in Trunk @ 9357 |
Date Modified | Username | Field | Change |
---|---|---|---|
2012-10-16 21:38 | Admiral MS | New Issue | |
2012-10-17 00:25 | Swifty | Assigned To | => Swifty |
2012-10-17 00:25 | Swifty | Status | new => assigned |
2012-10-22 19:16 | Admiral MS | Note Added: 0013991 | |
2012-10-26 08:00 | The_E | Note Added: 0013993 | |
2012-10-28 01:36 | Goober5000 | Target Version | => 3.6.16 |
2012-11-11 00:19 | Swifty | Note Added: 0014019 | |
2012-11-11 10:49 | Admiral MS | Note Added: 0014024 | |
2012-11-11 13:59 | MjnMixael | Note Added: 0014025 | |
2012-11-12 00:14 | Swifty | Note Added: 0014030 | |
2012-11-17 12:27 | m_m | Note Added: 0014045 | |
2012-11-17 16:32 | MjnMixael | Note Edited: 0014025 | |
2012-11-18 15:45 | FUBAR-BDHR | Note Added: 0014048 | |
2012-11-18 18:41 | Valathil | Note Added: 0014052 | |
2012-11-18 18:41 | Valathil | Status | assigned => resolved |
2012-11-18 18:41 | Valathil | Resolution | open => fixed |
2012-11-18 18:41 | Valathil | Assigned To | Swifty => Valathil |
2012-11-18 18:41 | Valathil | Status | resolved => feedback |
2012-11-18 18:41 | Valathil | Resolution | fixed => reopened |
2012-11-18 18:41 | Valathil | Status | feedback => resolved |
2012-11-18 18:41 | Valathil | Resolution | reopened => fixed |