http://bugs.winehq.org/show_bug.cgi?id=18901
Summary: WoW crashes on exit when running in D3D Product: Wine Version: 1.1.23 Platform: PC-x86-64 URL: http://www.worldofwarcraft.com OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d AssignedTo: wine-bugs@winehq.org ReportedBy: adys.wh@gmail.com
Created an attachment (id=21743) --> (http://bugs.winehq.org/attachment.cgi?id=21743) Backtrace
World of Warcraft, when ran in d3d mode, always crashes when exiting the game. Backtrace attached.
This is very annoying since settings, caches etc won't get saved if a crash happens.
http://bugs.winehq.org/show_bug.cgi?id=18901
--- Comment #1 from Henri Verbeet hverbeet@gmail.com 2009-06-12 05:46:19 --- Unfortunately that backtrace doesn't help much. Perhaps a +d3d,+d3d9 trace is usefull.
http://bugs.winehq.org/show_bug.cgi?id=18901
--- Comment #2 from Jerome Leclanche adys.wh@gmail.com 2009-06-12 08:27:12 --- (In reply to comment #1)
Unfortunately that backtrace doesn't help much. Perhaps a +d3d,+d3d9 trace is usefull.
Somehow I couldn't reproduce it only on the login screen anymore, I had to log in game. This makes the backtrace a lot bigger, sorry about that (350MB).
http://devcub.com/~adys/wow2.txt.lzma - 1.8MB is the lowest I can go and that can't be uploaded on bugzilla.
http://bugs.winehq.org/show_bug.cgi?id=18901
--- Comment #3 from Henri Verbeet hverbeet@gmail.com 2009-06-12 09:51:24 --- (In reply to comment #2)
trace:d3d:DestroyContext Destroying ctx 0x14c6f0 trace:d3d:DestroyContext Destroy dst FBO 1
...
trace:d3d:context_clean_fbo_attachments glFramebufferTexture2D() call ok context.c / 71 wine: Unhandled page fault on read access to 0x00000004 at address 0x7e007038 (thread 0009), starting debugger... Unhandled exception: page fault on read access to 0x00000004 in 32-bit code (0x7e007038). Register dump: CS:0023 SS:002b DS:002b ES:002b FS:0063 GS:006b EIP:7e007038 ESP:0039fb80 EBP:7ccbf7a0 EFLAGS:00010246( R- -- I Z- -P- ) EAX:00000000 EBX:7c3fd658 ECX:000000a1 EDX:00000000 ESI:00000000 EDI:00000000 Stack dump: 0x0039fb80: 7ccbf814 7cca4980 7ccbf814 7dd22211 0x0039fb90: 7ccb36a4 7ccbf814 7ccbf7c0 7cca4980 0x0039fba0: 7cc8f000 00000001 00000008 7daf5662 0x0039fbb0: 7cc8f000 00000000 7cca4980 7ccbf7a0 0x0039fbc0: 0380000c 7ccbf7a0 00000008 7cc8f000 0x0039fbd0: 00000000 00000000 00000000 7dfd0c2a Backtrace: =>0 0x7e007038 in libglcore.so.1 (+0x863038) (0x7ccbf7a0) 0x7e007038: movl 0x4(%eax),%eax
It seems to die on "glBindFramebufferEXT(GL_FRAMEBUFFER_EXT, 0);" in context_destroy_fbo(). I can't say for sure if this is our bug or something in the driver, but I don't see anything obvious we could be doing wrong. Perhaps nvidia has an idea about what's happening here.
http://bugs.winehq.org/show_bug.cgi?id=18901
Yann Droneaud yann@droneaud.fr changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |yann@droneaud.fr
--- Comment #4 from Yann Droneaud yann@droneaud.fr 2009-06-13 10:32:47 --- Backtrace looks like bug #18871
http://bugs.winehq.org/show_bug.cgi?id=18901
--- Comment #5 from Jerome Leclanche adys.wh@gmail.com 2009-06-13 11:38:31 --- (In reply to comment #4)
Backtrace looks like bug #18871
Could both be dupes of bug 18636?
http://bugs.winehq.org/show_bug.cgi?id=18901
--- Comment #6 from Henri Verbeet hverbeet@gmail.com 2009-06-17 04:25:30 --- (In reply to comment #5)
(In reply to comment #4)
Backtrace looks like bug #18871
Could both be dupes of bug 18636?
Certainly looks like the same problem. 18871 is the easiest to reproduce, and I can at least reproduce the problem here now, but only on GF9, GF7 appears to work fine.
http://bugs.winehq.org/show_bug.cgi?id=18901
--- Comment #7 from Jerome Leclanche adys.wh@gmail.com 2009-06-17 06:21:20 --- (In reply to comment #6)
(In reply to comment #5)
(In reply to comment #4)
Backtrace looks like bug #18871
Could both be dupes of bug 18636?
Certainly looks like the same problem. 18871 is the easiest to reproduce, and I can at least reproduce the problem here now, but only on GF9, GF7 appears to work fine.
FWIW, I got a GeForce 9800gtx+.
http://bugs.winehq.org/show_bug.cgi?id=18901
--- Comment #8 from Henri Verbeet hverbeet@gmail.com 2009-06-27 04:17:15 --- Created an attachment (id=22051) --> (http://bugs.winehq.org/attachment.cgi?id=22051) patch
Does this patch make it any better?
http://bugs.winehq.org/show_bug.cgi?id=18901
--- Comment #9 from Jerome Leclanche adys.wh@gmail.com 2009-06-27 05:48:55 --- (In reply to comment #8)
Created an attachment (id=22051)
--> (http://bugs.winehq.org/attachment.cgi?id=22051) [details]
patch
Does this patch make it any better?
Yes.
http://bugs.winehq.org/show_bug.cgi?id=18901
--- Comment #10 from Henri Verbeet hverbeet@gmail.com 2009-06-29 09:25:41 --- Should be fixed by 40565211fb70bff4b1622570a6b11edd646c00bd.
http://bugs.winehq.org/show_bug.cgi?id=18901
Jerome Leclanche adys.wh@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |FIXED
--- Comment #11 from Jerome Leclanche adys.wh@gmail.com 2009-07-17 10:05:14 --- (In reply to comment #10)
Should be fixed by 40565211fb70bff4b1622570a6b11edd646c00bd.
Indeed.
http://bugs.winehq.org/show_bug.cgi?id=18901
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #12 from Alexandre Julliard julliard@winehq.org 2009-07-17 12:29:59 --- Closing bugs fixed in 1.1.26.
http://bugs.winehq.org/show_bug.cgi?id=18901
Jerome Leclanche adys.wh@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Fixed by SHA1| |40565211fb70bff4b1622570a6b | |11edd646c00bd