cybersphinx changed status from new to closed

cybersphinx set resolution to duplicate

cybersphinx commented

Duplicate of #937.

Buginator changed status from closed to reopened

Buginator changed resolution from duplicate to ``

Buginator commented

Can you try again what you did before, and see if you have any text in your stderr.txt file (if on windows) or whatever output you get if on linux/mac?

This is most likely a video driver issue.

(in 2.2.4 we added another debug line for this issue, and it should spit out some new info, unless it crashes before this... that is why I reopened this ticket.

Buginator commented

NOTE: Trac is not updating people, so we can't use 'pending' until that is fixed.

anonymous commented

Ok, I'm not the author of this ticket, but I have the same problem. I'm running WinXp pro on administrator user account.

I was testing it on a campaing savegame. I deleted stderr.txt and crashed the game on Int. display. In happends sometimes after you open one of the items, doesnt really matter which one. Sometimes its the first you open, sometimes 3rd etc. In stderr.txt I got:

info |05:28:15: [rebuildSearchPath] * Failed to remove path C:\Program Files/data/\ again
info |05:28:15: [rebuildSearchPath] * Failed to remove path C:\Program Files/share/warzone2100/\ again

So, I created those directories. Then I tried crashing game again. It still crashes to desktop, but now stderr.txt is empty.

I analyzed warzone2100.rpt and found out that it contains the same information about each crash:

Program: C:\Program Files\Warzone 2100\warzone2100.exe(warzone2100)
Command line: "C:\Program Files\Warzone 2100\warzone2100.exe" 
Version: Version 2.2.4 (modified locally)
Distributor: wz2100.net
Compiled on: Oct 11 2009 15:15:45
Compiled by: GCC 4.2.1-sjlj (mingw32-2)
Compiled mode: Release build
Executed on: Wed Nov 04 17:43:23 2009

Pointers: 32bit

Compiled against PhysicsFS version: 1.0.1
Running with PhysicsFS version: 1.0.1

Misc Data:
[05:43:26]OpenGL Vendor : NVIDIA Corporation
[05:43:26]OpenGL Renderer : GeForce FX 5200/AGP/SSE
[05:43:26]OpenGL Version : 2.0.3
[05:43:26]OpenGL GLSL Version : 1.10 NVIDIA via Cg 1.3 compiler
[05:43:26]Video Mode 1024 x 768 (32 bpp) (fullscreen)
[05:43:27]OpenAL Vendor: Creative Labs Inc.
[05:43:27]OpenAL Version: 1.1
[05:43:27]OpenAL Renderer: Software
[05:43:27]OpenAL Extensions: EAX EAX2.0 EAX3.0 EAX4.0 EAX5.0 EAX3.0EMULATED EAX4.0EMULATED AL_EXT_OFFSET 

AL_EXT_LINEAR_DISTANCE AL_EXT_EXPONENT_DISTANCE
[05:43:27]Using language: English (United Kingdom)
[05:43:51]Current Level/map is SUB_1_5S


C:\Program Files\Warzone 2100\warzone2100.exe caused an Access Violation at location 00613f36 in module 

C:\Program Files\Warzone 2100\warzone2100.exe Reading from location 0731fff4.


Registers:
eax=00000058 ebx=00000000 ecx=0731fff4 edx=0382b0f0 esi=00000004 edi=0393e338
eip=00613f36 esp=0022e230 ebp=0383806c iopl=0         nv up ei pl nz na pe nc
cs=001b  ss=0023  ds=0023  es=0023  fs=003b  gs=0000             efl=00210202

Call stack:
00613F36  C:\Program Files\Warzone 2100\warzone2100.exe:00613F36

Buginator commented

Replying to Warzone2100/old-trac-import#1025 (comment:5):

Ok, I'm not the author of this ticket, but I have the same problem. I'm running WinXp pro on administrator user account.

I was testing it on a campaing savegame. I deleted stderr.txt and crashed the game on Int. display. In happends sometimes after you open one of the items, doesnt really matter which one. Sometimes its the first you open, sometimes 3rd etc. In stderr.txt I got:

info |05:28:15: [rebuildSearchPath] * Failed to remove path C:\Program Files/data/\ again
info |05:28:15: [rebuildSearchPath] * Failed to remove path C:\Program Files/share/warzone2100/\ again

So, I created those directories. Then I tried crashing game again. It still crashes to desktop, but now stderr.txt is empty.

Um, those are not errors per se, those are "info" lines... no need to worry about that. They are telling us that things are still open, and it can't unmount it yet.

I analyzed warzone2100.rpt and found out that it contains the same information about each crash:

Program: C:\Program Files\Warzone 2100\warzone2100.exe(warzone2100)
Command line: "C:\Program Files\Warzone 2100\warzone2100.exe" 
Version: Version 2.2.4 (modified locally)
Distributor: wz2100.net
Compiled on: Oct 11 2009 15:15:45
Compiled by: GCC 4.2.1-sjlj (mingw32-2)
Compiled mode: Release build
Executed on: Wed Nov 04 17:43:23 2009

Pointers: 32bit

Compiled against PhysicsFS version: 1.0.1
Running with PhysicsFS version: 1.0.1

Misc Data:
[05:43:26]OpenGL Vendor : NVIDIA Corporation
[05:43:26]OpenGL Renderer : GeForce FX 5200/AGP/SSE
[05:43:26]OpenGL Version : 2.0.3
[05:43:26]OpenGL GLSL Version : 1.10 NVIDIA via Cg 1.3 compiler
[05:43:26]Video Mode 1024 x 768 (32 bpp) (fullscreen)
[05:43:27]OpenAL Vendor: Creative Labs Inc.
[05:43:27]OpenAL Version: 1.1
[05:43:27]OpenAL Renderer: Software
[05:43:27]OpenAL Extensions: EAX EAX2.0 EAX3.0 EAX4.0 EAX5.0 EAX3.0EMULATED EAX4.0EMULATED AL_EXT_OFFSET 

AL_EXT_LINEAR_DISTANCE AL_EXT_EXPONENT_DISTANCE
[05:43:27]Using language: English (United Kingdom)
[05:43:51]Current Level/map is SUB_1_5S


C:\Program Files\Warzone 2100\warzone2100.exe caused an Access Violation at location 00613f36 in module 

C:\Program Files\Warzone 2100\warzone2100.exe Reading from location 0731fff4.


Registers:
eax=00000058 ebx=00000000 ecx=0731fff4 edx=0382b0f0 esi=00000004 edi=0393e338
eip=00613f36 esp=0022e230 ebp=0383806c iopl=0         nv up ei pl nz na pe nc
cs=001b  ss=0023  ds=0023  es=0023  fs=003b  gs=0000             efl=00210202

Call stack:
00613F36  C:\Program Files\Warzone 2100\warzone2100.exe:00613F36

Yes, and since there is no call stack, that means that it crashed outside of warzone, in the video (or sound, or ...) drivers.
Which means, that the fault of this is in something external. We can't fix external issues.

anonymous commented

Replying to Warzone2100/old-trac-import#1025 (comment:6):

Ok, I'm not a programmer, don't know what's important, so I give as much info as I can :)

I recently found out that this crash occurs much less, when I don't use video sequences. Game still crashed 1 or 2 times, but it was rare. I have the lo-fi version, maybe I'll try the hi-fi.
Or maybe it's a problem with video/sound codec?

Buginator changed status from reopened to closed

Buginator changed resolution from `` to external

Buginator commented

Closing as external.

This is most likely a video driver bug. You need to try older/newer drivers direct from the vendor's site, and if on windows, don't use windows update.

If you still think this is a issue with our codebase, then we need a way to replicate this. As it is now, using the available tools we have we don't seem to be breaking any openGL specs.