http://bugs.winehq.org/show_bug.cgi?id=22619
Summary: Regression causing loader.c: loader_section wait timed out in Tap'Touche Product: Wine Version: unspecified Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winmm&mci AssignedTo: wine-bugs@winehq.org ReportedBy: cerebro.alexiel@gmail.com CC: m.b.lankhorst@gmail.com
Hi,
I noticed a regression in this software. (Demo version can still be downloaded at http://www.demarque.com/download_demo/index.asp?noProduit=45fra) The bug occurs before seeing the main UI. So simply launch it and then click on "Quitter".
When it worked, console output was alex@Evan:~/.wine/drive_c/Program Files/Tap'Touche 5$ /home/alex/Projects/wine/wine ./TTouche.exe fixme:xrender:XRender_AlphaBlend not supported - XRENDER headers were missing at compile time fixme:system:SetProcessDPIAware stub! fixme:dwmapi:DwmIsCompositionEnabled 0x33cf64 fixme:iphlpapi:NotifyAddrChange (Handle 0xa6ce8c8, overlapped 0xa6ce8d0): stub fixme:bitblt:client_side_dib_copy potential optimization: client-side color-index mode DIB copy
but now I get alex@Evan:~/.wine/drive_c/Program Files/Tap'Touche 5$ /home/alex/Projects/wine/wine ./TTouche.exe fixme:bitblt:client_side_dib_copy potential optimization: client-side color-index mode DIB copy err:ntdll:RtlpWaitForCriticalSection section 0x68215864 "loader.c: loader_section" wait timed out in thread 001d, blocked by 001b, retrying (60 sec) wine: Critical section 68215864 wait failed at address 0x6819c088 (thread 001d), starting debugger... Unhandled exception: wait failed on critical section 0x68215864 loader_section err:seh:raise_exception Unhandled exception code c0000194 flags 0 addr 0x6819c088 Process of pid=001a has terminated No process loaded, cannot execute 'echo Modules:' Cannot get info on module while no process is loaded No process loaded, cannot execute 'echo Threads:' process tid prio (all id:s are in hex) 00000008 TTouche.exe 00000009 0 0000000e services.exe 00000014 0 00000010 0 0000000f 0 00000011 winedevice.exe 00000016 0 00000013 0 00000012 0 00000017 explorer.exe 00000018 0 You must be attached to a process to run this command. No process loaded, cannot execute 'detach'
I did a regression test and found alex@Evan:~/Projects/wine$ git bisect good 4f4dd855c47cca17d4b750ca118826614afdc20c is first bad commit commit 4f4dd855c47cca17d4b750ca118826614afdc20c Author: Maarten Lankhorst m.b.lankhorst@gmail.com Date: Wed Mar 31 20:19:35 2010 +0200
winmm: Defer loading drivers until they are requested.
:040000 040000 f3db7429aa6c8f870e6abd1f6328c5412731dbe1 3bd406034df5d9e5ddd9b2cdf8b8a51af36926ea M dlls
Reverting the patch solves the issue (even if `patch` failed to revert some part of this patch)
I pasted here some logs because I didn't want to add an attachment for some lines. If you think that's wrong, tell me and I won't do it again.
http://bugs.winehq.org/show_bug.cgi?id=22619
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |regression Summary|Regression causing |loader_section wait timed |loader.c: loader_section |out in Tap'Touche |wait timed out in | |Tap'Touche |
http://bugs.winehq.org/show_bug.cgi?id=22619
Dmitry Timoshkov dmitry@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Version|unspecified |1.1.43
http://bugs.winehq.org/show_bug.cgi?id=22619
--- Comment #1 from Alex cerebro.alexiel@gmail.com 2010-05-12 12:29:21 --- I don't know anything about winmm but WINEDEBUG="+winmm" gives some interesting traces (with latest git) :
trace:winmm:MMDRV_Install ('winealsa.drv', 'winealsa.drv', mapper=N); warn:winmm:MMDRV_Install Couldn't open driver 'winealsa.drv'
I guess it's not normal. I'm using SMPlayer (and so mplayer) with alsa output for playing almost everything and it works fine. But MMDRV_Install wineoss is ok though.
I got also trace:winmm:MMDRV_Get ((nil), 0003, Y) trace:winmm:MMDRV_GetByID (0000, 0003) trace:winmm:MMDRV_Message (MidiOut 0 2 0x00000000 0x0032ea7c 0x00000054) trace:winmm:MMDRV_Message Calling message(dev=0 msg=2 usr=0x00000000 p1=0x0032ea7c p2=0x00000054) trace:winmm:MMDRV_Message => MMSYSERR_NOERROR
and finally trace:winmm:MMDRV_GetByID (ffffffff, 0005) trace:winmm:MMDRV_Message (WaveOut 65535 4 0x00000000 0x0032f05c 0x00000054) trace:winmm:MMDRV_Message Calling message(dev=65535 msg=4 usr=0x00000000 p1=0x0032f05c p2=0x00000054) trace:winmm:MMDRV_GetNum (0005) trace:winmm:MMDRV_Message => MMSYSERR_BADDEVICEID
Are these relevant ? I can attach a more verbose log if anyone needs it.
http://bugs.winehq.org/show_bug.cgi?id=22619
Maarten Lankhorst m.b.lankhorst@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |DUPLICATE
--- Comment #2 from Maarten Lankhorst m.b.lankhorst@gmail.com 2010-05-17 12:56:41 --- dup
*** This bug has been marked as a duplicate of bug 22252 ***
http://bugs.winehq.org/show_bug.cgi?id=22619
--- Comment #3 from Alex cerebro.alexiel@gmail.com 2010-05-17 13:24:09 --- Glad to see that someone understands the issue and has a patch for it. I feared this bug was dead because the author of the breaking patch did not answer.
But I understand, there are lots of bugs, regressions ... and wine 1.2 is coming.
Anyway, I just wanted to say thanks.
http://bugs.winehq.org/show_bug.cgi?id=22619
Vitaliy Margolen vitaliy@kievinfo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #4 from Vitaliy Margolen vitaliy@kievinfo.com 2010-05-17 21:46:39 --- Closing dup.