http://bugs.winehq.org/show_bug.cgi?id=14348
Summary: Unhandled Exception code c0000005 Product: Wine Version: 1.0.0 Platform: All OS/Version: Linux Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: sdlyr8@gmail.com
I have wine working on my ubuntu distro (8.04) and I have no problems opening most exe files. But when I try to open the install.exe file for Diablo 2, I get the error
err:seh:raise_exception Unhandled exception code c0000005 flags 0 addr 0xb7d3225b
I have searched for days and i can't find a solution and a few times people have said it is a bug in Wine. Is there an older version I can fall back to?
Ubuntu 8.04 nVidia GeForce 6600 Dual Monitors wine 1.0
http://bugs.winehq.org/show_bug.cgi?id=14348
Mikolaj Zalewski mikolaj.zalewski@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |mikolaj.zalewski@gmail.com
--- Comment #1 from Mikolaj Zalewski mikolaj.zalewski@gmail.com 2008-07-08 02:46:58 --- Please attach the whole Wine output. You can redirect it to a file by running "wine something.exe &>output.txt"
http://bugs.winehq.org/show_bug.cgi?id=14348
Stephen Lindauer sdlyr8@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |sdlyr8@gmail.com
--- Comment #2 from Stephen Lindauer sdlyr8@gmail.com 2008-07-08 08:08:45 --- That IS the whole output. That one line is the only message I get.
http://bugs.winehq.org/show_bug.cgi?id=14348
Lei Zhang thestig@google.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Severity|enhancement |normal Summary|Unhandled Exception code |Diablo 2: Unhandled |c0000005 |Exception code c0000005
http://bugs.winehq.org/show_bug.cgi?id=14348
--- Comment #3 from Ken johnsonken1@gmail.com 2008-08-08 21:45:36 --- Created an attachment (id=15358) --> (http://bugs.winehq.org/attachment.cgi?id=15358) Results of trying to play Terminator 3
Installs, get sound from a .avi that plays, black screen.
http://bugs.winehq.org/show_bug.cgi?id=14348
Dmitry Timoshkov dmitry@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Platform|All |Other
http://bugs.winehq.org/show_bug.cgi?id=14348
Dmitry Timoshkov dmitry@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |jake.aikens@gmail.com
--- Comment #4 from Dmitry Timoshkov dmitry@codeweavers.com 2008-09-03 04:54:24 --- *** Bug 15108 has been marked as a duplicate of this bug. ***
http://bugs.winehq.org/show_bug.cgi?id=14348
Daniel Ehlers danielehlers@mindeye.net changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |danielehlers@mindeye.net
--- Comment #5 from Daniel Ehlers danielehlers@mindeye.net 2009-03-08 16:13:32 --- I have the same errors with Terminator 3, installs fine updating to 1.16 and gettings attached results.
http://bugs.winehq.org/show_bug.cgi?id=14348
--- Comment #6 from Daniel Ehlers danielehlers@mindeye.net 2009-03-08 16:14:31 --- Created an attachment (id=19840) --> (http://bugs.winehq.org/attachment.cgi?id=19840) console output from t3 run
http://bugs.winehq.org/show_bug.cgi?id=14348
--- Comment #7 from Xwarman@gmx.de 2009-08-15 15:04:25 --- Hi. I got those error if I tryed to start Diablo 2 LoD after installing from the webinstaller. (Downloadable from blizzards game site) After I'd run D2VidTst.exe in the gamefolder and specified the grafic modus of the game, it runs without any problems. Maybe that can help to fix the problem.
http://bugs.winehq.org/show_bug.cgi?id=14348
Mihály MÉSZÁROS poizon@sth.sze.hu changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |poizon@sth.sze.hu
--- Comment #8 from Mihály MÉSZÁROS poizon@sth.sze.hu 2009-08-16 08:23:05 --- On wine 1.1.26 runs diablo 2, but on 1.1.27 fails to start with this exception. Git bisect found the first bad commit: http://source.winehq.org/git/wine.git/?a=commit;h=4ab7af65750bbf0fc9ce16b15e...
http://bugs.winehq.org/show_bug.cgi?id=14348
Jerome Leclanche adys.wh@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |adys.wh@gmail.com, | |hverbeet@gmail.com
--- Comment #9 from Jerome Leclanche adys.wh@gmail.com 2009-08-29 00:26:46 --- CC Henri (PS, I had to search for a while to find the email you use on bugzilla, would be great if you could use the same one as your committer mail)
http://bugs.winehq.org/show_bug.cgi?id=14348
--- Comment #10 from Henri Verbeet hverbeet@gmail.com 2009-08-29 04:19:49 --- (In reply to comment #9)
CC Henri (PS, I had to search for a while to find the email you use on bugzilla, would be great if you could use the same one as your committer mail)
That's because I read wine-bugs, CC doesn't do anything anyway. The exception from comment 8 should no longer occur in 1.1.28.
http://bugs.winehq.org/show_bug.cgi?id=14348
Tim Donnelly glucosegrin@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Ever Confirmed|0 |1
--- Comment #11 from Tim Donnelly glucosegrin@gmail.com 2010-03-15 14:29:42 --- *** This bug has been confirmed by popular vote. ***
http://bugs.winehq.org/show_bug.cgi?id=14348
Tim Donnelly glucosegrin@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |glucosegrin@gmail.com
--- Comment #12 from Tim Donnelly glucosegrin@gmail.com 2010-03-15 14:33:43 --- I've got the same sort of error. c0000005 exception in Diablo 2, sometimes randomly, always when creating a private game in battle.net.
Wine v.1.1.40 Diablo 2 LoD downloaded v.1.12
http://bugs.winehq.org/show_bug.cgi?id=14348
--- Comment #13 from Tim Donnelly glucosegrin@gmail.com 2010-03-15 14:34:52 --- Created an attachment (id=26827) --> (http://bugs.winehq.org/attachment.cgi?id=26827) Log output with D2LoD v1.12 when crash occurs
http://bugs.winehq.org/show_bug.cgi?id=14348
Xavier Vachon xvachon@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |xvachon@gmail.com
--- Comment #14 from Xavier Vachon xvachon@gmail.com 2010-07-19 18:27:23 --- In current git (1.2), I was able to install Diablo 2, it's expansion and to start a game without experiencing the unhandled exception. Can Stephen and Tim test this again and confirm if this is fixed?
http://bugs.winehq.org/show_bug.cgi?id=14348
Oli Vhann3000@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |Vhann3000@gmail.com
http://bugs.winehq.org/show_bug.cgi?id=14348
--- Comment #15 from Oli Vhann3000@gmail.com 2010-11-23 21:22:05 CST --- Created an attachment (id=32100) --> (http://bugs.winehq.org/attachment.cgi?id=32100) Log output of winedbg upon wine crashing
http://bugs.winehq.org/show_bug.cgi?id=14348
--- Comment #16 from Oli Vhann3000@gmail.com 2010-11-23 21:23:40 CST --- I can confirm this bug to *NOT* be fixed.
I get this error in a predictable fashion: I do a 'taskset -p 2 wine Diablo II.exe' (being on a SMP system, Diablo II will crash if I let it run on multiple cores), create a single player game (or create a TCP/IP one) then I just have to talk to an NPC (Malah for example), it will work. As soon as I will talk to the NPC a second time though, I will get this error.
Attached is the error log winedbg produced when I killed the error popup window.
System details: Slackware64 13.1 wine 1.3.7
http://bugs.winehq.org/show_bug.cgi?id=14348
--- Comment #17 from Olivier Diotte Vhann3000@gmail.com 2010-11-24 23:14:46 CST --- (In reply to comment #16)
I can confirm this bug to *NOT* be fixed.
I get this error in a predictable fashion: I do a 'taskset -p 2 wine Diablo II.exe' (being on a SMP system, Diablo II will crash if I let it run on multiple cores)
I made some more tests: first, Diablo still works even if I let it run on multiple cores as it pleases: I had first compiled Wine in a 32 bits environment (namely, by setting the path to point to 32 bits versions of gcc and al. before the 64 bits versions). Now that I don't specify anything, it seems to be less prone to crashing.
Also, it seems that I can talk multiple times to an NPC without the game crashing if I wait for 1-2 seconds between each «talk». Clicking rapidly on the NPC makes the game crash with the same error though.
That is with Diablo II: LOD v1.13
http://bugs.winehq.org/show_bug.cgi?id=14348
--- Comment #18 from Olivier Diotte olivier@diotte.ca 2011-02-03 03:39:49 CST --- (In reply to comment #17)
I made some more tests: first, Diablo still works even if I let it run on multiple cores as it pleases: I had first compiled Wine in a 32 bits environment (namely, by setting the path to point to 32 bits versions of gcc and al. before the 64 bits versions). Now that I don't specify anything, it seems to be less prone to crashing.
Correction: the game still crashes no matter what I do.
The problem seems to lie into the wineserver (or the system calls the former makes) which the game doesn't seem to be very fond of.
I have been succesfully able to play (and click NPCs frenetically) without crashing by using the following trick:
first, su root: su -
then start a chroot jail at the current root (limiting the chroot to a single processor): taskset -p 1 chroot /
Now, su back to the non-root user (vhann in my case): su - vhann
Now launch 'wine Diablo\ II.exe' from within that shell and it'll work flawlessly.
http://bugs.winehq.org/show_bug.cgi?id=14348
--- Comment #19 from Olivier Diotte olivier@diotte.ca 2011-02-10 23:40:18 CST --- Haven't been able to reproduce this bug with 1.3.12
http://bugs.winehq.org/show_bug.cgi?id=14348
Alexey Loukianov mooroon2@mail.ru changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |mooroon2@mail.ru
--- Comment #20 from Alexey Loukianov mooroon2@mail.ru 2011-09-23 18:39:24 CDT --- I can't reproduce this bug on my system with Wine 1.3.28 and Diablo II LOD 1.13c. What are the exact steps should I take to try to reproduce this bug?
http://bugs.winehq.org/show_bug.cgi?id=14348
Viktor Yu. Kovalskiy vityokster@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |vityokster@gmail.com
--- Comment #21 from Viktor Yu. Kovalskiy vityokster@gmail.com 2011-12-27 11:16:40 CST --- I can reproduce this bug starting from wine-1.3.29 to wine-1.3.35 and current git version.
I try to find bad commit following by http://wiki.winehq.org/RegressionTesting I found that first bad commit is
b9fcf71c714e8587def75742f94759d7eca84ad2 is the first bad commit commit b9fcf71c714e8587def75742f94759d7eca84ad2 Author: Henri Verbeet hverbeet@codeweavers.com Date: Thu Sep 15 20:01:51 2011 +0200
ddraw: Use real flips.
:040000 040000 dde17c19243dd91a3830083879701b13c2a4476f 81d5b536d9f76c42bcdac7b3b3fb41814ebc6216 M dlls
I think that this crash links with wined3d subsystem like in comment 8
(In reply to comment #8)
On wine 1.1.26 runs diablo 2, but on 1.1.27 fails to start with this exception. Git bisect found the first bad commit: http://source.winehq.org/git/wine.git/?a=commit;h=4ab7af65750bbf0fc9ce16b15e...
But I can't confirm this bug for wine for 1.3.28 and earlier. I checked wine version 1.2.3 and from 1.3.12 to 1.3.29 and 1.3.35.
Gentoo ~x86 Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller
http://bugs.winehq.org/show_bug.cgi?id=14348
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |regression Regression SHA1| |b9fcf71c714e8587def75742f94 | |759d7eca84ad2
http://bugs.winehq.org/show_bug.cgi?id=14348
Henri Verbeet hverbeet@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords|regression | Regression SHA1|b9fcf71c714e8587def75742f94 | |759d7eca84ad2 |
--- Comment #22 from Henri Verbeet hverbeet@gmail.com 2011-12-28 00:06:08 CST --- Whatever this bug is about, it can't be a regression introduced by b9fcf71c714e8587def75742f94759d7eca84ad2, since the bug report predates that commit by several years. If b9fcf71c714e8587def75742f94759d7eca84ad2 breaks something for you please file a new bug report with a proper backtrace.
http://bugs.winehq.org/show_bug.cgi?id=14348
Rafa³ Mi³ecki zajec5@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |zajec5@gmail.com
--- Comment #23 from Rafa³ Mi³ecki zajec5@gmail.com 2012-02-03 14:09:07 CST --- I've been playing Diablo II for hours without any problems. After some break I tried again and I got exactly this error.
At first I suspected Wine regression, but reverting to some old Wine 1.3.24 (I know this version was working fine) didn't help. In meanwhile I updated openSUSE to 12.1 (from 11.3 or 11.4), so that was the next suspected.
It seems updating Mesa as part of openSUSE update broke something. Part of my glxinfo is like: OpenGL vendor string: X.Org OpenGL renderer string: Gallium 0.4 on AMD RV620 OpenGL version string: 2.1 Mesa 7.11
I've continued my tests with Wine 1.3.24. I've discovered that using software rendering avoids c0000005 problem!
BAD (Wine 1.3.24): wine ~/.wine/drive_c/Diablo\ II/Game.exe
GOOD (Wine 1.3.24): LIBGL_ALWAYS_SOFTWARE=1 wine ~/.wine/drive_c/Diablo\ II/Game.exe
GOOD (Wine 1.3.24): wine ~/.wine/drive_c/Diablo\ II/Game.exe -w
-w is a switch for running game in window instead of fullscreen
http://bugs.winehq.org/show_bug.cgi?id=14348
--- Comment #24 from Henri Verbeet hverbeet@gmail.com 2012-02-03 14:19:08 CST --- (In reply to comment #23)
It seems updating Mesa as part of openSUSE update broke something. Part of my glxinfo is like: OpenGL vendor string: X.Org OpenGL renderer string: Gallium 0.4 on AMD RV620 OpenGL version string: 2.1 Mesa 7.11
Does DRAW_USE_LLVM=0 make it any better? You don't mention a backtrace, and I suppose there may not be one if the game eats the exception, but what you describe sounds a bit like https://bugs.freedesktop.org/show_bug.cgi?id=41791 and similar bugs over at fd.o.
http://bugs.winehq.org/show_bug.cgi?id=14348
--- Comment #25 from Rafa³ Mi³ecki zajec5@gmail.com 2012-02-03 14:30:11 CST --- GOOD (Wine 1.3.24): DRAW_USE_LLVM=0 wine ~/.wine/drive_c/Diablo\ II/Game.exe
So yes, using DRAW_USE_LLVM=0 is another workaround. Unfortunately I can't use Wine git because of another regression I'm tracking right now. Will post more details after bisecting.
As for backtrace, I don't get any - at least by looking at stdout and stderr. Is there any magic wine switch to make it print backtrace? I think it's not Wine that is crashing, but it's application getting some not-trackable-for-Wine crash. You can Google for some (rare, but still...) Windows problem with "Unhandled Exception code c0000005" too.
http://bugs.winehq.org/show_bug.cgi?id=14348
--- Comment #26 from Henri Verbeet hverbeet@gmail.com 2012-02-03 14:45:04 CST --- (In reply to comment #25)
As for backtrace, I don't get any - at least by looking at stdout and stderr. Is there any magic wine switch to make it print backtrace?
If Wine doesn't automatically print one you can sometimes still manually get one with winedbg, but if DRAW_USE_LLVM=0 helps it probably not worth the effort. My impression is that there's just something broken about the way the SUSE 32-bit Mesa packages link to LLVM. I suppose you could also just try gdb, the crash is probably in Mesa / r600_dri.so, somewhere during draw module initialization. This doesn't have a whole lot to do with Wine though.
I think it's not Wine that is crashing, but it's application getting some not-trackable-for-Wine crash. You can Google for some (rare, but still...) Windows problem with "Unhandled Exception code c0000005" too.
c0000005 is a pretty generic access violation, it doesn't tell you much on its own.
http://bugs.winehq.org/show_bug.cgi?id=14348
Luis Sánchez lusadi@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |lusadi@gmail.com
--- Comment #27 from Luis Sánchez lusadi@gmail.com 2012-03-12 19:45:25 CDT --- Im over Arch Linux x64, intel 4500M graphic card, wine version 1.4, I run Diablo LOD Web installer 1.12, the installer run perfect but when i run diablo a windows show "Unhandled Exception code c0000005"
I solve the problem installing the "lib32-intel-dri", the game works fine, battlenet too.
I install lib32-intel-dri and a problem with google earth is gone too.
http://bugs.winehq.org/show_bug.cgi?id=14348
--- Comment #28 from Alexey Loukianov mooroon2@mail.ru 2012-03-15 11:32:48 CDT --- (In reply to comment #27)
Im over Arch Linux x64, intel 4500M graphic card, wine version 1.4, I run Diablo LOD Web installer 1.12, the installer run perfect but when i run diablo a windows show "Unhandled Exception code c0000005"
I solve the problem installing the "lib32-intel-dri", the game works fine, battlenet too.
I install lib32-intel-dri and a problem with google earth is gone too.
Your case has nothing to do either with original bug report and/or with the latest _new_bugs_ caused by LLVM optimizations used by latest Mesa as packaged with openSUSE 12.1. As Henri had already posted here, exception c0000005 is a pretty generic one and it can be caused by a number of things (for example, as a result of heap corruption caused by buggy kernel modules and/or system lib).
In your case is seems that you had been merely trying to start up 32bit game on a 64bit system lacking required GL support libraries, namely intel-dri, which are required to be able to use 32bit Mesa's libGL.
As for this bug: it seems that it had been hi-jacked several times and also had been abandoned by original reporter. Maybe, it's just the right time to close it "ABADONED" and/or "OBSOLETE", as most likely this bug is no longer valid after all that years that passed since original reporting date. Dmitry, Vitaliy, what do you think?
http://bugs.winehq.org/show_bug.cgi?id=14348
Johannes Obermayr johannesobermayr@gmx.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |johannesobermayr@gmx.de
--- Comment #29 from Johannes Obermayr johannesobermayr@gmx.de 2012-10-29 17:06:09 CDT --- Maybe here is the fix: http://cgit.freedesktop.org/mesa/mesa/commit/?id=eaa8e56108e28ff5fabc8c471f4...
http://bugs.winehq.org/show_bug.cgi?id=14348
--- Comment #30 from Viktor Yu. Kovalskiy vityokster@gmail.com 2012-11-05 08:44:38 CST --- I have installed wine-1.5.16, mesa-9.0, xf86-video-intel-2.20.12 and I have successful running Diablo II LoD 1.13d without any errors.
Only I should choose DirectDraw (2D): DirectDraw HAL.
If I choose Direct3D I have missing textures.
http://bugs.winehq.org/show_bug.cgi?id=14348
Zach Steele zcsteele@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |zcsteele@gmail.com
--- Comment #31 from Zach Steele zcsteele@gmail.com 2012-12-29 19:50:54 CST --- I ran into this issue in wine 1.5.20, running on Mint 13 (64-bit). I was able to correct the error by installing directmusic via winetricks.
http://bugs.winehq.org/show_bug.cgi?id=14348
--- Comment #32 from Bruno Jesus 00cpxxx@gmail.com --- Is this still an issue in wine 1.7.11 or later?
http://bugs.winehq.org/show_bug.cgi?id=14348
Frédéric Delanoy frederic.delanoy@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |frederic.delanoy@gmail.com Resolution|--- |ABANDONED
--- Comment #33 from Frédéric Delanoy frederic.delanoy@gmail.com --- Abandoned.
Feel free to reopen if the problem persists in the latest wine version.
http://bugs.winehq.org/show_bug.cgi?id=14348
Frédéric Delanoy frederic.delanoy@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #34 from Frédéric Delanoy frederic.delanoy@gmail.com --- Closing
-
wine-bugs＠winehq.org