http://bugs.winehq.org/show_bug.cgi?id=26414
Summary: Unhandled exception: page fault on read access to 0x5f6f760c in 32-bit code (0x7d665da1). Product: Wine Version: 1.3.15 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: tim.kornhammar@gmail.com
Used the app World of warcraft and Wine crashed while changing the display resolution.
Version: wine-1.3.15 Distribution: Ubuntu 10.10 - Maverick Meerkat Program: World Of Warcraft (blizzard.com) Command: wine .wine/drive_c/Program\ Files/World\ of\ Warcraft/Wow.exe
Reproduce: Change resolution (any to any)
http://bugs.winehq.org/show_bug.cgi?id=26414
Dmitry Timoshkov dmitry@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Summary|Unhandled exception: page |World of warcraft crashes |fault on read access to |while changing the display |0x5f6f760c in 32-bit code |resolution |(0x7d665da1). |
--- Comment #1 from Dmitry Timoshkov dmitry@codeweavers.com 2011-03-14 10:11:34 CDT --- Please attach terminal output as described at http://wiki.winehq.org/FAQ#get_log
http://bugs.winehq.org/show_bug.cgi?id=26414
--- Comment #2 from Dmitry Timoshkov dmitry@codeweavers.com 2011-03-14 10:13:06 CDT --- *** Bug 26415 has been marked as a duplicate of this bug. ***
http://bugs.winehq.org/show_bug.cgi?id=26414
--- Comment #3 from Tim Kornhammar tim.kornhammar@gmail.com 2011-03-14 10:29:52 CDT --- Created an attachment (id=33635) --> (http://bugs.winehq.org/attachment.cgi?id=33635) Terminal output.
http://bugs.winehq.org/show_bug.cgi?id=26414
--- Comment #4 from Tim Kornhammar tim.kornhammar@gmail.com 2011-03-14 10:30:36 CDT --- Wierd that it didn't get included on reporting it but now it is attached..
http://bugs.winehq.org/show_bug.cgi?id=26414
--- Comment #5 from Tim Kornhammar tim.kornhammar@gmail.com 2011-03-14 10:51:52 CDT --- Created an attachment (id=33636) --> (http://bugs.winehq.org/attachment.cgi?id=33636) More info in this log.
http://bugs.winehq.org/show_bug.cgi?id=26414
André H. nerv@dawncrow.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |nerv@dawncrow.de
http://bugs.winehq.org/show_bug.cgi?id=26414
--- Comment #6 from Austin English austinenglish@gmail.com 2011-03-14 14:54:52 CDT --- (In reply to comment #0)
Command: wine .wine/drive_c/Program\ Files/World\ of\ Warcraft/Wow.exe
cd to the directory first.
What video card/drivers?
http://bugs.winehq.org/show_bug.cgi?id=26414
--- Comment #7 from Tim Kornhammar tim.kornhammar@gmail.com 2011-03-14 14:57:11 CDT --- Should I ad a new log?
Graphics: xserver-xorg-video-ati (1:6.14.99+git20110307.6319a33c-0ubuntu0sarvatt~maverick)
http://bugs.winehq.org/show_bug.cgi?id=26414
--- Comment #8 from Tim Kornhammar tim.kornhammar@gmail.com 2011-03-16 13:43:56 CDT --- I've never debugged Wine before but I do know both c an c++ so if you could point me in the right direction maybe I can dig some in the code?
http://bugs.winehq.org/show_bug.cgi?id=26414
--- Comment #9 from André H. nerv@dawncrow.de 2011-03-16 13:58:43 CDT --- you may want to read http://wiki.winehq.org/Developers but basically you can turn on traces of specific dlls/files with WINEDEBUG. e.g. WINEDEBUG=wininet wine app.exe and of course you can add your on to your local codebase to see more.
As it crashes in wow you we can't see why here. But if you use the relay debug channel you see nearly every important call and if you read through it you normally see why an app crashes that bad way
http://bugs.winehq.org/show_bug.cgi?id=26414
--- Comment #10 from Tim Kornhammar tim.kornhammar@gmail.com 2011-03-18 04:26:22 CDT --- Created an attachment (id=33695) --> (http://bugs.winehq.org/attachment.cgi?id=33695) Winedbg log.
I used winedbg and got some additional information on the crash.
Wow crashed, I started winedbg and did a 'bt all'. As I understand it now it shows where it crashed.
In that case there is some functions called *WaitForMultipleObjects* that crashes Wine?
http://bugs.winehq.org/show_bug.cgi?id=26414
--- Comment #11 from Juan Lang juan_lang@yahoo.com 2011-03-18 11:47:30 CDT --- (In reply to comment #10)
In that case there is some functions called *WaitForMultipleObjects* that crashes Wine?
No. The crash is a NULL pointer access in the application, not a crash in Wine. The application is probably receiving a NULL pointer it doesn't expect to get, and guessing the source of it is usually the difficult part.
http://bugs.winehq.org/show_bug.cgi?id=26414
--- Comment #12 from Tim Kornhammar tim.kornhammar@gmail.com 2011-03-18 13:15:33 CDT --- I suppose this is one part where Wine should handle the null pointer instead of crashing.
How do I proceed in triaging where World of Warcraft call that makes Wine crash comes from?
http://bugs.winehq.org/show_bug.cgi?id=26414
--- Comment #13 from Austin English austinenglish@gmail.com 2011-03-18 13:17:24 CDT --- (In reply to comment #12)
I suppose this is one part where Wine should handle the null pointer instead of crashing.
How do I proceed in triaging where World of Warcraft call that makes Wine crash comes from?
+relay,+seh,+tid is usually a good start.
http://bugs.winehq.org/show_bug.cgi?id=26414
--- Comment #14 from Tim Kornhammar tim.kornhammar@gmail.com 2011-03-18 16:51:58 CDT --- Log file (5MB gz): http://www.ludd.ltu.se/~scuba/winedebug.gz
I tried the WINEDEBUG but to me it doesn't really say anything about the crash.
Does it say anything to you or any new direction I can take?
http://bugs.winehq.org/show_bug.cgi?id=26414
fastjack dvconci@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |dvconci@gmail.com
--- Comment #15 from fastjack dvconci@gmail.com 2011-03-21 09:05:23 CDT --- I tried in Debian Squeeze (6.0) with wine 1.0 and WoW run very well. In Ubuntu 10.10 (Maverick) i tried in wine versions: 1.0, 1.2 and 1.3: All fail changing resolution... but if i wait a error come up saying Cannot estabilish comunication with wow server... and when i try use wine to navigate on internet its don't go. In Debian 6.0 go ok, and Ubuntu 10.10 not... maybe a distro config...?
Sorry my pour english... thanks.
http://bugs.winehq.org/show_bug.cgi?id=26414
--- Comment #16 from butraxz@gmail.com 2013-09-15 07:40:56 CDT --- This ticket has not been updated for over 900 days. Development recommends to check the status on your bug every release or two and let to be known if the bug is still present. If not, mark it fixed. If you are no longer able to put effort to this ticket, you can abandon it.
Is this still an issue with 1.7.2 or higher ?
https://bugs.winehq.org/show_bug.cgi?id=26414
gpiez@web.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |gpiez@web.de
--- Comment #17 from gpiez@web.de --- Using 1.7.25 on an nvidia card, it runs fine for me if I change the resolution.
https://bugs.winehq.org/show_bug.cgi?id=26414
odielag@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |odielag@gmail.com
--- Comment #18 from odielag@gmail.com --- I cannot confirm this bug.
I run wow retail on a radeon hd7850 in opensuse 13.1 with wine 1.7.25 and both in opengl and directx I can fullscreen/window/fullscreenwindow.
OS: OpenSuSE 13.1 Wine: 1.7.25 (opensuse oneclick install) Graphics: Radeon hd7850 (opensuse one click install proprietary) wow: current retail as of this post
https://bugs.winehq.org/show_bug.cgi?id=26414
--- Comment #19 from André H. nerv@dawncrow.de --- (In reply to odielag from comment #18)
I cannot confirm this bug.
I run wow retail on a radeon hd7850 in opensuse 13.1 with wine 1.7.25 and both in opengl and directx I can fullscreen/window/fullscreenwindow.
Have you also tried different resolutions? like changing from 1920x### to 1280x### ?
https://bugs.winehq.org/show_bug.cgi?id=26414
--- Comment #20 from odielag@gmail.com --- I cannot confirm this bug because wine did not crash when I switched resolutions.
---------- I just tried changing the resolutions while running in 'Fullscreen' mode.
I have a 1920x1200 monitor and a 1600x900 display.
With it showing on the 1920x1200 monitor at 1920x1200 resolution I switched resolutions to 1024x768 and the display jumped to the smaller monitor without the mouse able to enter the window. This would be a different issue (but small I think because)...
When I switched it to a '(Wide)' resolution above 1024x768 it remained on the original monitor.
To sum things up, wine didn't crash for me when I switched resolutions. ----------
Wine: 1.7.26 (opensuse one click install) OS: Opensuse 13.1 x64 Wow: Current retail as of this post (5.4.?) running the Wow-64.exe directly. Graphics: Radeon HD7850 with proprietary drivers installed with opensuse oneclick.
https://bugs.winehq.org/show_bug.cgi?id=26414
André H. nerv@dawncrow.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED
--- Comment #21 from André H. nerv@dawncrow.de --- marking fixed as of comments 17 & 20
https://bugs.winehq.org/show_bug.cgi?id=26414
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #22 from Alexandre Julliard julliard@winehq.org --- Closing bugs fixed in 1.7.27.