http://bugs.winehq.org/show_bug.cgi?id=24181
Summary: Bioshock v1.1 crashes when run, but remains playable Product: Wine Version: 1.1.31 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: wylda@volny.cz
Bioshock v1.1 crashes when run, but remains playable. This happens only when patch 1.1 is applied. The trace log is same in 1.1.31 and 1.3.1 so adding actual version.
Another interesting thing, limiting to just one core (schedtool -a 0x1 -e wine) doesn't make the problem go away :c(
1. I did a regression test between 1.1.30 and 1.1.31:
commit 474b2e4bfb46cf1bb8db0faa6ecfdb3fd157b117 Author: Juan Lang juan.lang@gmail.com Date: Tue Sep 29 09:17:30 2009 -0700
server: Use kernel support for thread affinity when available.
:100755 100755 ceb6e205078fc890e211ee9d2fbd7939135cb5ff d05447a9edce4b7826498ee87062591e6e76d45a M configure :100644 100644 d489f007d41cbc2ccfb4b12417db324f2fcc7540 27ae652560eea4893e4d5944ef1fbe44c29263cc M configure.ac :040000 040000 1e0f37ea233c8ba15132512313dbdf2bb3e77654 ad140066e30159cd5854e06c82f6fec682060600 M include :040000 040000 52e94800e61abf27e898a7450887a1403d1687c1 2f44cf433e78754b96cd498d7c2c958ade307d06 M server
2. There are another bug reports where this commit helps, even though Juan had some doubts: http://bugs.winehq.org/show_bug.cgi?id=20602#c7
3. Revert of this patch after git checkout makes that problem go away.
4. Adding author of this patch to CC.
--private keyword: bisected
http://bugs.winehq.org/show_bug.cgi?id=24181
Wylda wylda@volny.cz changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |regression CC| |juan_lang@yahoo.com
http://bugs.winehq.org/show_bug.cgi?id=24181
--- Comment #1 from Wylda wylda@volny.cz 2010-08-28 06:13:05 CDT --- Created an attachment (id=30441) --> (http://bugs.winehq.org/attachment.cgi?id=30441) console output from wine-1.3.1-267-g7ab48e8
http://bugs.winehq.org/show_bug.cgi?id=24181
--- Comment #2 from Juan Lang juan_lang@yahoo.com 2010-08-30 11:23:51 CDT --- Please attach a +relay,+seh,+tid trace of the crash.
http://bugs.winehq.org/show_bug.cgi?id=24181
--- Comment #3 from Wylda wylda@volny.cz 2010-08-31 03:37:51 CDT --- Created an attachment (id=30492) --> (http://bugs.winehq.org/attachment.cgi?id=30492) console output from wine-1.3.1-320-g39b9814 +relay,+seh,+tid last 100K
(In reply to comment #2)
Please attach a +relay,+seh,+tid trace of the crash.
Last 100'000 lines of requested log. If anything missing, i can provide more or filtered original or point me to some upload place.
http://bugs.winehq.org/show_bug.cgi?id=24181
--- Comment #4 from Juan Lang juan_lang@yahoo.com 2010-09-07 11:46:58 CDT --- The crash appears to be a divide by zero, but I don't see what it's doing just before the crash, so I'm afraid I don't know the reason for it.
http://bugs.winehq.org/show_bug.cgi?id=24181
--- Comment #5 from Wylda wylda@volny.cz 2010-09-07 12:14:54 CDT --- (In reply to comment #4)
The crash appears to be a divide by zero, but I don't see what it's doing just before the crash, so I'm afraid I don't know the reason for it.
The log wasn't long enough? Could i do something more here? (logs, debug channels...)
http://bugs.winehq.org/show_bug.cgi?id=24181
--- Comment #6 from Juan Lang juan_lang@yahoo.com 2010-09-07 13:24:52 CDT --- (In reply to comment #5)
The log wasn't long enough? Could i do something more here? (logs, debug channels...)
No, that's not it. I just don't know what the program is doing that results in the crash. Is the crash reproduceable with the demo, perhaps?
http://bugs.winehq.org/show_bug.cgi?id=24181
--- Comment #7 from Austin English austinenglish@gmail.com 2010-10-12 17:44:03 CDT --- (In reply to comment #6)
(In reply to comment #5)
The log wasn't long enough? Could i do something more here? (logs, debug channels...)
No, that's not it. I just don't know what the program is doing that results in the crash. Is the crash reproduceable with the demo, perhaps?
Potentially, but it works fine for me, after installing native d3dx_36 for bug 23884. I think it's based on 1.0...
http://bugs.winehq.org/show_bug.cgi?id=24181
Dan Kegel dank@kegel.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |dank@kegel.com
--- Comment #8 from Dan Kegel dank@kegel.com 2011-02-03 10:53:55 CST --- Wylda, does the problem go away if you use the cpuset facility to limit the game to one core? (cpuset is very different from schedtool, it is a stronger container.) Alternately, does booting with nosmp hide the problem?
http://bugs.winehq.org/show_bug.cgi?id=24181
Wylda wylda@volny.cz changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords|regression | Status|NEW |RESOLVED Resolution| |INVALID
--- Comment #9 from Wylda wylda@volny.cz 2011-06-18 19:58:57 CDT ---
Hmmm... It seems that i was wrong here. The crash was here already, but since that Juan's commit it just moved _before_ the game switched to graphics.
When i was doing the regression test, i was looking for the point, when it begins to show up at the startup. When i knew good/bad, i was saving time and killed that game and went for another round. If i quit correctly, then on exit i would noticed, that the crash is still there (was hiden in the background).
Marking as invalid, as this report is messed up. Sorry for that.
http://bugs.winehq.org/show_bug.cgi?id=24181
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #10 from Austin English austinenglish@gmail.com 2011-07-07 16:15:51 CDT --- Closing.
-
wine-bugs＠winehq.org