[Bug 59209] Monster Truck Madness 2 takes very long when loading/leaving a race

[WineHQ Bugzilla]

http://bugs.winehq.org/show_bug.cgi?id=59209

Bernhard Übelacker <[e-mail]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #1 from Bernhard Übelacker <[e-mail]> ---
This wait time might be related to a 16-bit process,
that gets started by Monsterx.EXE:

C:\windows\syswow64\winevdm.exe --app-name C:\windows\system32\dispdib.dll
C:\windows\system32\DISPDIB.DLL


At least the first seems to be needed.
On following runs killing that process makes the game to continue.


Further inspecting the thread that starts the subprocess shows this:

1016539.057:0148:014c:Call KERNEL32.LoadModule(0064a07c "DISPDIB.DLL",0031fd40)
ret=0053769e
...
1016539.057:0148:014c:trace:unixpid:CreateProcessInternalW app
L"C:\\windows\\system32\\DISPDIB.DLL" cmdline
L"C:\\windows\\system32\\DISPDIB.DLL " :527
...
1016539.113:0148:014c:Ret  ntdll.RtlFreeUnicodeString() retval=00000000
ret=7b6c1c3c
1016569.114:0148:014c:Ret  KERNEL32.LoadModule() retval=00000021 ret=0053769e


So the LoadModule call takes 30 seconds, which looks kind of intentional:

149         if (CreateProcessA( filename, cmdline, NULL, NULL, FALSE, 0,
150                             params->lpEnvAddress, NULL, &startup, &info ))
151         {
152             /* Give 30 seconds to the app to come up */
153             if (wait_input_idle) wait_input_idle( info.hProcess, 30000 );


But still not sure, maybe there is some event missing
from DISPDIB to the parent process.

-- 
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.