http://bugs.winehq.org/show_bug.cgi?id=32282
Bug #: 32282 Summary: Wine crashes randomly and often with Catalyst driver>12.9 Product: Wine Version: 1.5.14 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: nob.dir.info@gmail.com Classification: Unclassified
I tested all version of Wine in the 1.5 branch, and I found that with Wine 1.5.14 and further, games like League of Legends, Portal 2 or Guild Wars 2 are crashing really often and randomly (in fact, X.org freeze as well as my mouse and my keyboard, and I have then to restart my PC).
I didn't have time to proceed to a regression testing yet, but I will do it.
Cordially, nob.
http://bugs.winehq.org/show_bug.cgi?id=32282
nob.dir.info@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |nob.dir.info@gmail.com
http://bugs.winehq.org/show_bug.cgi?id=32282
nob.dir.info@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Severity|normal |major
http://bugs.winehq.org/show_bug.cgi?id=32282
nob.dir.info@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Summary|Wine crashes randomly and |Playing games makes the |often with Catalyst |system freezes randomly and |driver>12.9 |often with Catalyst | |driver>12.9
http://bugs.winehq.org/show_bug.cgi?id=32282
nob.dir.info@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |hverbeet@gmail.com Regression SHA1| |49f9d394934109e13fe76a9605a | |ed505efc3d089
--- Comment #1 from nob.dir.info@gmail.com 2012-11-25 09:04:36 CST --- I proceeded the regression test. I found that the patch which causes this bug is http://source.winehq.org/git/wine.git/commit/49f9d394934109e13fe76a9605aed50... done by Henri.
http://bugs.winehq.org/show_bug.cgi?id=32282
nob.dir.info@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Component|-unknown |directx-d3d
http://bugs.winehq.org/show_bug.cgi?id=32282
Henri Verbeet hverbeet@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |UPSTREAM
--- Comment #2 from Henri Verbeet hverbeet@gmail.com 2012-11-25 09:50:04 CST --- Anything that causes X to freeze or the machine to lockup is by definition not a Wine issue, since Wine is a regular userspace application. The bisect result you got also looks extremely unlikely, since all it does is change some internals of how GLSL shaders are generated. The worst that would happen if something is wrong in there is that shaders would start failing to compile.
http://bugs.winehq.org/show_bug.cgi?id=32282
nob.dir.info@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |UNCONFIRMED Resolution|UPSTREAM |
--- Comment #3 from nob.dir.info@gmail.com 2012-11-25 10:20:48 CST --- It's strange too, but catalyst and its mysteries... Furthermore, I never got errors in X.org logs and in dmesg... I read your patch (I never worked with GLSL, so I can't really understand it), but could the fact you use _ in the patch make any difference?
http://bugs.winehq.org/show_bug.cgi?id=32282
nob.dir.info@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |UPSTREAM
--- Comment #4 from nob.dir.info@gmail.com 2012-11-25 10:21:27 CST --- Forgot to let the state resolved upstream...
http://bugs.winehq.org/show_bug.cgi?id=32282
--- Comment #5 from Henri Verbeet hverbeet@gmail.com 2012-11-25 11:24:23 CST --- (In reply to comment #3)
GLSL, so I can't really understand it), but could the fact you use _ in the patch make any difference?
Well, if there's e.g. memory corruption involved just about anything can make a difference, but it really shouldn't.
http://bugs.winehq.org/show_bug.cgi?id=32282
--- Comment #6 from nob.dir.info@gmail.com 2012-11-25 11:33:27 CST --- Ok, that's why... When I play, fglrx is spamming errors about memory corruption in dmesg... But normally it doesn't make anything crashes...
https://bugs.winehq.org/show_bug.cgi?id=32282
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #7 from Austin English austinenglish@gmail.com --- Closing.
https://bugs.winehq.org/show_bug.cgi?id=32282
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|CLOSED |RESOLVED
--- Comment #8 from Austin English austinenglish@gmail.com --- This was inadvertently caught up in my unclosed bugs filter. NOTOURBUG should only be closed when fixed upstream.
Setting back to RESOLVED NOTOURBUG.
Sorry for the spam.
-
wine-bugs＠winehq.org