[Bug 4904] Critical error when trying to start warcraft 3

[Wine Bugs]

http://bugs.winehq.org/show_bug.cgi?id=4904





------- Additional Comments From sini.ruohomaa at cs.helsinki.fi  2006-21-07 12:49 -------
Created an attachment (id=2978)
 --> (http://bugs.winehq.org/attachment.cgi?id=2978&action=view)
Warcraft Errors/ log on the pointer crash

Hi,
I have a very similar problem, but the address pointed to is consistently a
full 0.
FATAL ERROR!

Program:	Z:\home\opt\Warcraft III\War3.exe
Exception:	0xC0000005 (ACCESS_VIOLATION) at 0073:6F0B98D9

The instruction at '0x6F0B98D9' referenced memory at '0x00000000'.
The memory could not be 'read'.

In addition, this leaves X squeezed to a smaller resolution and somewhat
confused (window manager tooltips lag, etc); until I used -opengl, I could
never see the contents of the error window the game pops up (just the gray
background), but discovered the error from Warcraft's logs instead (crash log
with stack dump attached). Now I successfully saw the error window contents
referring to the access problem, but still can't click 'ok' on it since the
mouse cursor disappears over the error window - ps aux|grep wine shows one
wineserver process, maybe something else is crashed. 

My X is the latest from Ubuntu Dapper, 7.0.0, and all X-related packages
(presumably including DRI things) are up-to-date (the package manager only
tells me I could install yet another minor update to my linux-kernel
2.6.17-16-k7). I also just updated my wine form the Dapper 0.9.9 to 0.9.17, and
the problem is repeated on it. I have a Radeon video card using the "radeon"
driver, seems to be called Radeon 9200 PRO according to lspci. 

Another possible error source I can't yet completely shake loose is a dyslexic
optical station, which sometimes freezes in kernel calls resulting from
umount/mount or eject. I haven't noticed actual e.g. I/O errors, though. The
dma_intr errors are {DriveReady SeekComplete Error} and {DriveStatusError
BadCRC}. I will try this on a working CD station when I get the opportunity to
eliminate this possibility.

-- 
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.