http://bugs.winehq.org/show_bug.cgi?id=29505
Bug #: 29505 Summary: Regression: WINE crashes on start up of Mozart11 Product: Wine Version: 1.3.35 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: blocker Priority: P2 Component: msxml3 AssignedTo: wine-bugs@winehq.org ReportedBy: let02do@earthlink.net Classification: Unclassified
Created attachment 38213 --> http://bugs.winehq.org/attachment.cgi?id=38213 Console output when WINE crashes
The Mozart 11 software worked a bit sluggishly but reliably with wine-1.3.34. Beginning with wine-1.3.35, WINE has a crash and freeze when Mozart11 is starting. This is a complete show stopper and continues in wine-1.3.36, and the latest git (cloned on 12-30-2011). Another Mozart user who likes to keep WINE up to date has the same result.
With Linux/Kde/wine-1.3.35 through 1.3.36, WINE draws part of the Mozart UI then has a total lock-up that needs a "kill -9 <PID>" as root to rid the desktop of the zombie process. This seems to be a regression.
Running bisect ends with this result:
let01@arc:~/wine-git$ git bisect good a4b24978e9dc2e54057552fc2efffbd58cc25d0a is first bad commit commit a4b24978e9dc2e54057552fc2efffbd58cc25d0a Author: Nikolay Sivov nsivov@codeweavers.com Date: Fri Dec 9 14:02:10 2011 +0300
msxml3: Use libxml2 buffer support through helpers.
:040000 040000 f42af388fcd59844a1d5ac163e59cae14183785f 9f1d3e3120ff12f3f85c54c55365668ae33fcc3b M dlls
Looking at the commit date of Dec 9 I see that this was after the 1.3.34 release in which Mozart had no crash at start up. This is consistent with the problem showing up in 1.3.35 as noted.
I'm attaching the console output for the git . It ends with an exception followed by "Killed" The Alsa fixme's seem to be no problem in previous versions or in the bisect tests that did not show the bug
http://bugs.winehq.org/show_bug.cgi?id=29505
Lawrence E Toal let02do@earthlink.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |regression URL| |http://www.mozart.co.uk/pro | |grams/mzsetup.exe CC| |let02do@earthlink.net
http://bugs.winehq.org/show_bug.cgi?id=29505
Michael Stefaniuc mstefani@redhat.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |mstefani@redhat.com Regression SHA1| |a4b24978e9dc2e54057552fc2ef | |ffbd58cc25d0a
http://bugs.winehq.org/show_bug.cgi?id=29505
Lawrence E Toal let02do@earthlink.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #38213|0 |1 is obsolete| |
--- Comment #1 from Lawrence E Toal let02do@earthlink.net 2012-01-02 00:15:33 CST --- Created attachment 38214 --> http://bugs.winehq.org/attachment.cgi?id=38214 Console output when WINE crashes
http://bugs.winehq.org/show_bug.cgi?id=29505
Dmitry Timoshkov dmitry@baikal.ru changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |bunglehead@gmail.com Summary|Regression: WINE crashes on |Mozart11 crashes on start |start up of Mozart11 |up Severity|blocker |normal
http://bugs.winehq.org/show_bug.cgi?id=29505
Dmitry Timoshkov dmitry@baikal.ru changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |download
http://bugs.winehq.org/show_bug.cgi?id=29505
Nikolay Sivov bunglehead@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Component|msxml3 |-unknown Ever Confirmed|0 |1 Regression SHA1|a4b24978e9dc2e54057552fc2ef | |ffbd58cc25d0a |
--- Comment #2 from Nikolay Sivov bunglehead@gmail.com 2012-01-02 09:29:19 CST --- Well, I can't confirm this is msxml related, cause +msxml is empty for this application. Also even if it was a msxml regression this commit can't be a problem cause it just rearranges some calls with no functional changes.
Please try to run regression test again, for now I'm detaching this from msxml* component.
http://bugs.winehq.org/show_bug.cgi?id=29505
--- Comment #3 from Lawrence E Toal let02do@earthlink.net 2012-01-02 12:02:11 CST --- OK, I didn't see anything unusual in the bisect process, but I'll start over from scratch with a fresh clone of git as of today.
http://bugs.winehq.org/show_bug.cgi?id=29505
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |julliard@winehq.org Component|-unknown |gdi32 Regression SHA1| |82e1a4616cd4802e2c14c057732 | |f6296be73580b
--- Comment #4 from Austin English austinenglish@gmail.com 2012-01-02 13:36:52 CST --- austin@aw21 ~/wine-git $ git bisect bad 82e1a4616cd4802e2c14c057732f6296be73580b is the first bad commit commit 82e1a4616cd4802e2c14c057732f6296be73580b Author: Alexandre Julliard julliard@winehq.org Date: Sat Dec 10 13:27:16 2011 +0100
gdi32: Make sure that biSizeImage always contains the correct size in internal BITMAPINFO structures.
:040000 040000 64bcef12ed66371734d56f4b6a49ca923e0c6e6d a2fe84b5ea43ea2958855328ce06dff8ffcf3ba8 M dlls
http://bugs.winehq.org/show_bug.cgi?id=29505
Nikolay Sivov bunglehead@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC|bunglehead@gmail.com |
http://bugs.winehq.org/show_bug.cgi?id=29505
--- Comment #5 from Lawrence E Toal let02do@earthlink.net 2012-01-02 16:24:41 CST --- Thanks Austin English, I don't know why I didn't git your result the first time, but this time through the process it ended with:
let01@arc:~/wine-git$ git bisect bad 82e1a4616cd4802e2c14c057732f6296be73580b is first bad commit commit 82e1a4616cd4802e2c14c057732f6296be73580b Author: Alexandre Julliard julliard@winehq.org Date: Sat Dec 10 13:27:16 2011 +0100
gdi32: Make sure that biSizeImage always contains the correct size in internal BITMAPINFO structures.
:040000 040000 64bcef12ed66371734d56f4b6a49ca923e0c6e6d a2fe84b5ea43ea2958855328ce06dff8ffcf3ba8 M dlls
just as yours did.
I did notice that after this bisect:
let01@arc:~/wine-git$ git bisect good Bisecting: 100 revisions left to test after this (roughly 7 steps) [3e1af081c02b01b513137d33b3972fb0d34e811d] include: Remove unneeded extern "C" directives.
The Bug symptoms changed slightly to a more graceful crash that did not freeze the partly drawn UI on the desktop. Wine closed by itself after the crash.
At this point, I went to the "git bisect bad" branch, and the original freezing symptoms returned. Following that branch led to our similar results. Would it be useful to reset the bisect to that step and try the "git bisect good" branch? I.E. are two different bugs happening?
http://bugs.winehq.org/show_bug.cgi?id=29505
--- Comment #6 from Austin English austinenglish@gmail.com 2012-01-02 16:30:25 CST --- (In reply to comment #5)
At this point, I went to the "git bisect bad" branch, and the original freezing symptoms returned. Following that branch led to our similar results. Would it be useful to reset the bisect to that step and try the "git bisect good" branch? I.E. are two different bugs happening?
Possibly, though likely more DIB engine changes affected the behavior. I'd say wait until this bug is fixed before hunting for more bugs.
http://bugs.winehq.org/show_bug.cgi?id=29505
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Fixed by SHA1| |ccfbcfaf538ef6bf52e09a0d97e | |8ae6784718478 Status|NEW |RESOLVED Resolution| |FIXED
--- Comment #7 from Alexandre Julliard julliard@winehq.org 2012-01-03 13:29:28 CST --- Fixed by ccfbcfaf538ef6bf52e09a0d97e8ae6784718478.
http://bugs.winehq.org/show_bug.cgi?id=29505
--- Comment #8 from Lawrence E Toal let02do@earthlink.net 2012-01-03 16:16:33 CST --- Excellent!
I did a
git fetch ; git rebase origin
Compiled again, and the bug is indeed gone. Mozart's overall performance also seems a bit improved from what it was in wine-3.3.34. Well and quickly done, thanks.
http://bugs.winehq.org/show_bug.cgi?id=29505
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #9 from Alexandre Julliard julliard@winehq.org 2012-01-13 13:50:17 CST --- Closing bugs fixed in 1.3.37.