https://bugs.winehq.org/show_bug.cgi?id=37922
Anastasius Focht focht@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords|dotnet | URL|http://unity3d.com/unity/do |https://web.archive.org/web |wnload/download-windows |/20160404064109/http://down | |load.unity3d.com/download_u | |nity/UnitySetup-4.6.0.exe
--- Comment #2 from Anastasius Focht focht@gmx.net --- Hello folks,
revisiting, still present.
It takes some patience to reproduce, as already mentioned years ago. After creating 7 new projects I finally got a UI freeze and corresponding output in console.
Prerequisites: none (native .NET Framework not needed anymore)
--- snip --- $ pwd /home/focht/.wine/drive_c/Program Files (x86)/Unity/Editor
$ WINEDEBUG=+loaddll wine ./Unity.exe ... 0490:err:ntdll:RtlpWaitForCriticalSection section 7BC6D1E0 "/home/focht/projects/wine/mainline-src/dlls/ntdll/loader.c: loader_section" wait timed out in thread 0490, blocked by 0508, retrying (60 sec) 0490:err:ntdll:RtlpWaitForCriticalSection section 7BC6D1E0 "/home/focht/projects/wine/mainline-src/dlls/ntdll/loader.c: loader_section" wait timed out in thread 0490, blocked by 0508, retrying (60 sec) --- snip ---
tid = 0508 -> 1288 dec = Mono GC? thread tid = 0490 -> 1168 dec = main thread
Attaching with debugger to unity process and dumping the thread stack in question does prove it's exactly the same problem (function return addresses match).
--- snip --- Address To From Comment
1484FD8C F7D2A1A2 F7FE8559 F7FE8559 1484FDB4 7BC0B96C F7D2A1A2 F7D2A1A2 1484FDC8 0B76B081 7BC0B96C ntdll._NtClose@4+C 1484FDD8 0B76B555 0B76B081 mono.0B76B081 1484FDE8 0B7108F2 0B76B555 mono.0B76B555 1484FDFC 0B77743B 0B7108F2 mono.0B7108F2 1484FE3C 0B7774E3 0B77743B mono.0B77743B 1484FE48 7BC26F56 0B7774E3 mono.0B7774E3 1484FE68 7BC29C5F 7BC26F56 ntdll._call_dll_entry_point+16 1484FF2C 7BC29A02 7BC29C5F ntdll.MODULE_InitDLL+17F 1484FF48 7BC49DA6 7BC29A02 ntdll.LdrShutdownThread+D2 1484FF58 7B624748 7BC49DA6 ntdll.RtlExitUserThread+26 1484FF6C 7BC49CB7 7B624748 kernel32.@BaseThreadInitThunk@12+18 1484FF78 7BC49E47 7BC49CB7 ntdll._call_thread_func_wrapper+17 1484FFF0 00000000 7BC49E47 ntdll.call_thread_func+87 --- snip ---
Exiting thread 1288 has suspend count = 1 while holding the loader lock.
--- snip --- Numb ID Entry TEB EIP S Priority Name
6 1224 00000000 7FF02000 F7FE8557 0 Normal 4 1192 00000000 7FF62000 F7FE8557 0 Normal 2 1176 00000000 7FFA2000 F7FE8557 2 Normal Main 1168 00000000 7FFC2000 F7FE8559 0 Normal Main Thread 7 1228 00000000 7FEF2000 F7FE8557 0 Normal 5 1196 00000000 7FF52000 F7FE8559 0 TimeCritical 3 1188 00000000 7FF72000 F7FE8557 0 Normal 1 1172 00000000 7FFB2000 F7FE8557 1 Normal 8 1288 00000000 7FE12000 F7FE8559 1 Normal Mono gc thread? 12 1364 00000000 155D2000 F7FE8559 1 Normal 9 1300 00000000 7FDE2000 F7FE8559 1 Normal 13 1368 00000000 155C2000 F7FE8559 1 Normal 10 1304 00000000 7FE32000 F7FE8559 1 Normal 11 1340 00000000 7FF82000 F7FE8559 1 Normal 14 1372 00000000 155B2000 F7FE8557 0 Normal 15 1376 00000000 155A2000 F7FE8559 1 Normal 16 1380 00000000 15592000 F7FE8557 0 Normal 17 1384 00000000 15582000 F7FE8557 0 Normal 18 1524 7BC397F0 155F2000 F7FE8559 0 Normal --- snip ---
Still an interesting problem for sure - exposed by Mono bug. But then again, quoting myself:
--- quote --- There are various reports from Windows users that Unity3D crashes or freezes for them this problem might be present on Windows too, making this bug report invalid. --- quote ---
Not sure if it's worth the time. Probably only few people use old Unity3D 4.6 for development nowadays.
$ sha1sum UnitySetup-4.6.0.exe 5cc7a85e186c965d230bcc7a2a463d92fbc2f7fc UnitySetup-4.6.0.exe
$ du -sh UnitySetup-4.6.0.exe 1.3G UnitySetup-4.6.0.exe
$ wine --version wine-6.0-rc2
Regards