https://bugs.winehq.org/show_bug.cgi?id=49476 Dmitry Skvortsov (Iglu47) <lvb.crd(a)protonmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lvb.crd(a)protonmail.com --- Comment #17 from Dmitry Skvortsov (Iglu47) <lvb.crd(a)protonmail.com> --- (In reply to Kron4ek from comment #15)
Besides, if i enable full debug with WINEDEBUG="+all", the game gives me different error than with debug disabled, does this mean that there is a race condition somewhere?.
I don't know if this is the same regression or if it requires a separate bug report (a problem with the Battle.net launcher, does not allow me to do an accurate bisecting test). But I looked at wine-6.0rc3.r0.g56e7cd12ce0 with WINEDEBUG="-all,+relay" - it helps and the game started on my machine. (It seems to work from the versions after which the Battle.net launcher works.) When changing to WINEDEBUG="" or adding '&> /dev/null' the game crashes the CrashMailer popup appears. ``` EXCEPTION_ACCESS_VIOLATION writing to 0x0000003400360077 **Crashing Thread** (ID: 1112) DBG-ADDR<0000000140E5AE46>() DBG-ADDR<0000000140E3CD92>() DBG-ADDR<0000000140E5F9EC>() DBG-ADDR<0000000141802533>() ``` Please specify what kind of information will be useful. -- 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.