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

[WineHQ Bugzilla]

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

Anastasius Focht <focht at gmx.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |focht at gmx.net
           Keywords|                            |dotnet, Installer

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

the 'bt all' doesn't seem to match your console output. There are way too many
differences in the thread ids. Even if thread 006e has died while owning
lock(s), many other threads blocked by it don't appear in winedbg list.

Please provide console and winedbg logs from the same run. Include 'info
process' and 'info thread' output as well.

Your 'bt all' shows it's already happening at .NET Framework 4.5 verb. Does
testing 'winetricks -q dotnet45' exhibit the same problems?

--- snip ---
Backtracing for thread 0009 in process 0008
(Y:\dotnet45\dotnetfx45_full_x86_x64.exe):
--- snip ---

Also try to make a "lightweight" trace log if possible:

--- snip ---
$ WINEDEBUG=+timestamp,+pid,+seh,+process,+loaddll ... >>log.txt 2>&1
--- snip ---

Relay logs would be rather huge and make the issue potentially disappear.

FYI I can't reproduce it here with Wine 5.5. It successfully installed ten
consecutive times, each with clean 64-bit WINEPREFIX.

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.