Crash on campaign / tutorial start (when going into the actual game) - access violation

wzdev-ci commented 15 years ago

keyword_sisgl.dll_access_violation_sis resolution_external type_bug | by Angld

Error occured on Sunday, October 18, 2009 at 16:18:09.

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: Sun Oct 18 16:17:11 2009

Pointers: 32bit

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

Misc Data:
[04:17:15]OpenGL Vendor : SiS
[04:17:15]OpenGL Renderer : 661 VGA
[04:17:15]OpenGL Version : 1.4.0
[04:17:15]OpenGL GLSL Version : (null)
[04:17:15]Video Mode 640 x 480 (32 bpp) (window)
[04:17:20]OpenAL Vendor: Creative Labs Inc.
[04:17:20]OpenAL Version: 1.1
[04:17:20]OpenAL Renderer: Software
[04:17:20]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
[04:17:20]Using language: System locale

**C:\Program Files\Warzone 2100\warzone2100.exe caused an Access Violation at location 6912616d in module C:\WINDOWS\system32\sisgl.dll Reading from location 00000000.**

Log message: info    |04:17:27: [seq_Play] unable to open 'sequences/devastation.ogg' for playback
Log message: info    |04:17:29: [seq_Play] unable to open 'sequences/titles.ogg' for playback
Log message: info    |04:17:29: [seq_Play] unable to open 'sequences/devastation.ogg' for playback
Log message: info    |04:17:29: [seq_Play] unable to open 'sequences/titles.ogg' for playback
Log message: info    |04:17:29: [seq_Play] unable to open 'sequences/devastation.ogg' for playback
Log message: info    |04:17:29: [seq_Play] unable to open 'sequences/titles.ogg' for playback
Log message: info    |04:17:29: [seq_Play] unable to open 'sequences/devastation.ogg' for playback
Log message: info    |04:17:30: [seq_Play] unable to open 'sequences/titles.ogg' for playback
Log message: info    |04:17:30: [seq_Play] unable to open 'sequences/devastation.ogg' for playback
Log message: info    |04:17:30: [seq_Play] unable to open 'sequences/titles.ogg' for playback
Log message: info    |04:17:30: [seq_Play] unable to open 'sequences/devastation.ogg' for playback
Log message: info    |04:17:31: [seq_Play] unable to open 'sequences/titles.ogg' for playback
Log message: info    |04:17:31: [seq_Play] unable to open 'sequences/devastation.ogg' for playback
Log message: info    |04:17:32: [seq_Play] unable to open 'sequences/titles.ogg' for playback
Log message: info    |04:17:32: [seq_Play] unable to open 'sequences/devastation.ogg' for playback
Log message: info    |04:17:32: [seq_Play] unable to open 'sequences/titles.ogg' for playback
Log message: info    |04:17:32: [seq_Play] unable to open 'sequences/devastation.ogg' for playback
Log message: info    |04:18:08: [seq_Play] unable to open 'sequences/cam1/c001.ogg' for playback
Log message: info    |04:18:09: [rebuildSearchPath] * Failed to remove path C:\Program Files/data/\ again
Log message: info    |04:18:09: [rebuildSearchPath] * Failed to remove path C:\Program Files/share/warzone2100/\ again

Registers:
eax=00000080 ebx=057eb160 ecx=6917fc50 edx=6917fc50 esi=00000000 edi=00000004
eip=6912616d esp=0022ed78 ebp=0022ed88 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:
6912616D  C:\WINDOWS\system32\sisgl.dll:6912616D
69127EDD  C:\WINDOWS\system32\sisgl.dll:69127EDD
69128082  C:\WINDOWS\system32\sisgl.dll:69128082
690D1EC2  C:\WINDOWS\system32\sisgl.dll:690D1EC2
004FCE37  C:\Program Files\Warzone 2100\warzone2100.exe:004FCE37  newPage  /home/admins/wz2.2/2.2.4/src/texture.c:110
004FD397  C:\Program Files\Warzone 2100\warzone2100.exe:004FD397  texLoad  /home/admins/wz2.2/2.2.4/src/texture.c:211
00417811  C:\Program Files\Warzone 2100\warzone2100.exe:00417811  dataTERTILESLoad  /home/admins/wz2.2/2.2.4/src/data.c:806
005770DD  C:\Program Files\Warzone 2100\warzone2100.exe:005770DD  resLoadFile  /home/admins/wz2.2/2.2.4/lib/framework/frameresource.c:480
0057BFAB  C:\Program Files\Warzone 2100\warzone2100.exe:0057BFAB  res_parse  /home/admins/wz2.2/2.2.4/lib/framework/resource_parser.y:117
00576A75  C:\Program Files\Warzone 2100\warzone2100.exe:00576A75  resLoad  /home/admins/wz2.2/2.2.4/lib/framework/frameresource.c:121
0047AA2B  C:\Program Files\Warzone 2100\warzone2100.exe:0047AA2B  levLoadData  /home/admins/wz2.2/2.2.4/src/levels.c:723
0048167E  C:\Program Files\Warzone 2100\warzone2100.exe:0048167E  startGameLoop  /home/admins/wz2.2/2.2.4/src/main.c:550
00483293  C:\Program Files\Warzone 2100\warzone2100.exe:00483293  runTitleLoop  /home/admins/wz2.2/2.2.4/src/main.c:717
005A06AA  C:\Program Files\Warzone 2100\warzone2100.exe:005A06AA
005A0892  C:\Program Files\Warzone 2100\warzone2100.exe:005A0892
005A0349  C:\Program Files\Warzone 2100\warzone2100.exe:005A0349
004010A7  C:\Program Files\Warzone 2100\warzone2100.exe:004010A7  __mingw_CRTStartup  /home/ron/devel/debian/mingw32-runtime/mingw32-runtime-3.13/build_dir/src/mingw-runtime-3.13-20070825-1/crt1.c:237
00401123  C:\Program Files\Warzone 2100\warzone2100.exe:00401123

The same error occurs with version 2.2.1

Issue migrated from trac:1008 at 2022-04-15 19:52:48 -0700

wzdev-ci commented 15 years ago

Angld commented

Running it vanilla, so I don't know why it says modified locally.

Anyway, When I click begin campaign/skirmish or host game, the game quits with no given error. The above is output into warzone2100.RPT.

After searching, I believe it may have something to do with my graphic card (or lack thereof - this is integrated graphics).

wzdev-ci commented 15 years ago

Zarel edited the issue description

wzdev-ci commented 15 years ago

Zarel commented

Don't worry about "modified locally".

Crash here: http://developer.wz2100.net/browser/tags/2.2.4/src/texture.c#L110

wzdev-ci commented 15 years ago

anonymous commented

Replying to Warzone2100/old-trac-import#1008 (comment:1):

After searching, I believe it may have something to do with my graphic card (or lack thereof - this is integrated graphics).

Correct It crashed in your video driver sisgl.dll

wzdev-ci commented 15 years ago

Per changed keywords from sisgl.dll access violation to sisgl.dll access violation sis

wzdev-ci commented 15 years ago

Per changed component from Engine: Resource Management to Engine: Graphics

wzdev-ci commented 15 years ago

Per commented

Can you run the program with the command line option "--debug texture", then post the resulting stdout.txt and stderr.txt here?

wzdev-ci commented 15 years ago

parke.bostrom@... commented

I have also encountered the same bug, with the sisgl.dll driver.

It looks like a NULL pointer error. Maybe a function is returning NULL (as an error) and WZ2100 is not checking for NULL? (Or maybe it is a bug in the driver.)

This bug started with version 2.1.x. I can run version 2.0.10 just fine.

Did WZ2100 start using a new version of OpenGL between 2.0.x and 2.1.x?

I will try attaching the the "--debug texture" output files.

wzdev-ci commented 15 years ago

parke.bostrom@... _uploaded file 20091029_stderr.txt (10.1 KiB)_

sisgl.dll --debug texture stderr file

wzdev-ci commented 15 years ago

parke.bostrom@... _uploaded file 20091029_warzone2100.RPT (4.7 KiB)_

sisgl.dll --debug texture rpt file

wzdev-ci commented 15 years ago

cybersphinx commented

This looks like you don't have enough RAM for your graphics card. Maybe you can raise the amount in the BIOS, or reduce texture size further to 32. If that doesn't help, there isn't much else for you to do (though maybe we want to check for available graphics ram when uploading textures, and abort with a clear error message).

wzdev-ci commented 15 years ago

parke.bostrom@... commented

I set the texture size to 32.

In the BIOS I set the integrated graphics to an "aperture" size of 256MB and a shared memory size of 128MB. (I have a total of 1GB of RAM on the system.) Warzone still crashes, exactly as before.

What are the minimum memory requirements?

What are the minimum graphics requirements? What version of OpenGL or DirectX?

Did the above requirements change between 2.0.x and 2.1.x?

Thanks!

wzdev-ci commented 15 years ago

cybersphinx commented

Hm, that should be enough RAM, 2.2 needs less than 64 MB (with default texture size). OpenGL 1.4 should be ok, I'm not sure what functionality we use, but not much more than 1.2 I think. Some of the used functions changed between 2.0 and 2.1, though I don't remember the specifics.

Unfortunately the drivers of those cheap integrated chips are usually quite crappy, so if up(or down)grading those doesn't help, we cannot do much about it (well, maybe if you can find out the exact change that makes 2.1+ crash). If Sis still make graphics chips, complain to them to fix their drivers.

wzdev-ci commented 14 years ago

Buginator changed status from new to closed

wzdev-ci commented 14 years ago

Buginator set resolution to external

wzdev-ci commented 14 years ago

Buginator commented

This is a crash in the video drivers, and as cybersphinx said, we can't really do anything if the video drivers crash.

Hopefully, they will have better drivers by now.

Closing as a external issue (video driver bug)

Warzone2100 / old-trac-import

Crash on campaign / tutorial start (when going into the actual game) - access violation #1008