[Bug 48847] dotnet471: often gets a critical section timeout

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=48847

--- Comment #6 from Anastasius Focht <focht at gmx.net> ---
Hello Austin,

--- snip ---
Wine-dbg>info process
 pid      threads  executable (all id:s are in hex)
 0000019d 1        'winedbg.exe'
 0000001b 4        'explorer.exe'
 0000000e 10       'services.exe'
 000000d8 4        \_ 'mscorsvw.exe'
 000000c7 5        \_ 'rpcss.exe'
 000000c0 7        \_ 'svchost.exe'
 00000020 5        \_ 'winedevice.exe'
 00000019 3        \_ 'plugplay.exe'
 00000011 4        \_ 'winedevice.exe'
 00000008 1        'NDP461-KB3102436-x86-x64-AllOS-ENU.exe'
 0000002e 5        \_ 'Setup.exe'
 0000003c 2           \_ 'msiexec.exe'
 00000059 14             \_ 'ngen.exe'
 0000017d 5                 \_ 'mscorsvw.exe'
 00000179 6                 \_ 'mscorsvw.exe'
 000000a6 12                \_ 'mscorsvw.exe'

Wine-dbg>info thread
process  tid      prio (all id:s are in hex)
00000008 NDP461-KB3102436-x86-x64-AllOS-ENU.exe
    00000009    0
...
00000059 ngen.exe
    0000018e    0
    0000014b    0
    00000137    0
    0000011b    0
    00000117    0
    00000102    0
    00000100    0
    000000a7    0
    00000132    0
    00000116    0
    0000010e    0
    0000010b    0
    00000108    0
    0000005a    0
--- snip ---

--- snip ---
...
0105:err:ole:ifproxy_release_public_refs IRemUnknown_RemRelease failed with
error 0x800706be
0105:err:ole:ifproxy_release_public_refs IRemUnknown_RemRelease failed with
error 0x800706be
0105:err:ole:ifproxy_release_public_refs IRemUnknown_RemRelease failed with
error 0x800706be
0105:err:ole:ifproxy_release_public_refs IRemUnknown_RemRelease failed with
error 0x800706be
0105:err:ole:ifproxy_release_public_refs IRemUnknown_RemRelease failed with
error 0x800706be
...
0105:fixme:ole:NdrClearOutParameters (01BEF664,008FAC56,01BEFD9C): stub
0105:err:seh:setup_exception_record stack overflow 756 bytes in thread 0105 eip
1008f936 esp 01af103c stack 0x1af0000-0x1af1000-0x1bf0000
00a7:err:ntdll:RtlpWaitForCriticalSection section 0x110060 "heap.c: main
process heap section" wait timed out in thread 00a7, blocked by 0105, retrying
(60 sec)
0100:err:ntdll:RtlpWaitForCriticalSection section 0x110060 "heap.c: main
process heap section" wait timed out in thread 0100, blocked by 0105, retrying
(60 sec)
0132:err:ntdll:RtlpWaitForCriticalSection section 0x110060 "heap.c: main
process heap section" wait timed out in thread 0132, blocked by 0105, retrying
(60 sec)
0108:err:ntdll:RtlpWaitForCriticalSection section 0x7bd2c220 "loader.c:
loader_section" wait timed out in thread 0108, blocked by 0132, retrying (60
sec)
014b:err:ntdll:RtlpWaitForCriticalSection section 0x7bd2c220 "loader.c:
loader_section" wait timed out in thread 014b, blocked by 0132, retrying (60
sec)
011b:err:ntdll:RtlpWaitForCriticalSection section 0x7bd2c220 "loader.c:
loader_section" wait timed out in thread 011b, blocked by 0132, retrying (60
sec)
0137:err:ntdll:RtlpWaitForCriticalSection section 0x7bd2c220 "loader.c:
loader_section" wait timed out in thread 0137, blocked by 0132, retrying (60
sec)
...
--- snip ---

Thread 0105 seems to be the culprit here. It was likely belonging to ngen
client (010x tid range). Happened maybe during update of GAC ('ngen update' /
'ngen executeQueuedItems').

If that's the case you could try to force run GAC update continuously (loop)
after installation and see if it breaks at some point (tee + grep for
exception/timeout patterns in output).

--- snip ---
# 32-bit assemblies
$ wine "c:\\windows\\Microsoft.NET\\Framework\\v4.0.30319\\ngen.exe" update

# 64-bit assemblies
$ wine "c:\\windows\\Microsoft.NET\\Framework64\\v4.0.30319\\ngen.exe" update
--- snip ---

Regards

-- 
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.