http://bugs.winehq.org/show_bug.cgi?id=13615
--- Comment #8 from GyB gyebro69@gmail.com 2010-05-09 12:31:13 --- Created an attachment (id=27827) --> (http://bugs.winehq.org/attachment.cgi?id=27827) crashlog running under winedbg
The issue still exists in Wine-1.1.44. The demo version also shows the same crash on the Spying/Diplomacy screens.
Link to the demo: http://www.fileplanet.com/35911/30000/fileinfo/Imperium-Galactica-II
How to reproduce the crash in the demo: 1. Start the demo, select 'Single Player' > 'Scenario' > choose the first scenario. 2. When the game is loaded press <F7> to get to the Spying screen. 3. Scroll through the available agent list, give him a new mission...the game will freeze in a short period of time.
This is a long-standing bug, I went back as far as wine-0.9.33, the same crash happens in every tested version. The crash always happens on the same screens (Spying/Diplomacy), but the generated backtraces varies from time to time, depending whether the game is started w/o sounds, which scenario you chose, what graphical details were set ingame etc. I'm not a programmer at all, but isn't it somewhat heap related?
The attached log was created when the game was started with audio disabled. I added WINEDEBUG=-d3d7 to eliminate printing the millions of fixmes: 'err:d3d7:IDirect3DDeviceImpl_3_GetRenderState Unexpected texture stage state setup, returning D3DTBLEND_MODULATE - likely erroneous'. They're present right after starting the game and I don't think it has something to do with the crash: the game doesn't crash if you don't use the mentioned Spying or Diplomacy screens.
I think starting the game with the right debug channels would reveal more info for an expert than the generated backtrace...if I knew which channels should be enabled.