http://bugs.winehq.org/show_bug.cgi?id=59236 --- Comment #9 from sldev <sldev@free.fr> --- (In reply to Louis Lenders from comment #7)
Could you run like:
WINEDLLOVERRIDES=powershell.exe,libcef=d WINEDEBUG=+relay,+seh wine SecondLifeViewer.exe &>/tmp/log
and attach ,after bzipping it, it here or put it up somewhere?
It's over 30GB big, so even once bzipped, it's a bit too much to handle. :-D You'll therefore find log3-head-100000.txt and log3-tail-100000.txt in the DebugLog.zip archive I just attached: they contain respectively the 100k first and 100k last lines of a session that did crash: sadly, the debugger fails to open when using +relay, so I don't have the corresponding backtrace... Amusingly, when enabling +relay, which causes an enormous slow down of the viewer (3 or so minutes to log in), the bug does not always happen, and sometimes the viewer does not crash. This could be the sign of some race condition at play: maybe Wine is failing to take a lock on some resource (the viewer is heavily threaded and when slowing things down, race conditions might become less likely to happen)... You will also find backtrace.txt and full log.txt files for a session done with just +seh.
You said you built wine yourself; to rule out that that might be the issue,
FYI, I've been building Wine for many, many years (IIRC my first personal Wine build was 3.0). But to reassure you and rule out such an issue:
it might be worth to try a prebuilt wine to see if that changes anything. I always use the builts from kron4ek:
Did this (also fully uninstalled my own Wine build before using your pre-built Wine, and used proper PATH and LD_LIBRARY_PATH exports to the unpacked Wine binaries). Exact same result (with the exception of a new "wine: failed to start L"C:\\windows\\system32\\winemenubuilder.exe": c0000135" warning, due to the fact that, unlike mine, your pre-built Wine does not have the wine32 stuff included). See the log2.txt and backtrace2.txt for the corresponding session/crash. -- 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.