https://bugs.winehq.org/show_bug.cgi?id=48006 --- Comment #49 from Chiitoo <chiitoo(a)gentoo.org> --- (In reply to Andrew Church from comment #48)
so either something is still missing or there is an extreme performance issue.
Yeah, I wonder what actually is going on there, as I noticed the 'ffxivlauncher64' process using almost 2 threads of a Ryzen 9 7950X while stuck for an eternity, but did not yet profile it or anything to pin it down. One time when running with 'all' debug channels open, I got the launcher turn into white, as if it might have gotten past it, ready to load the next page, but I did end up killing it after some time without visible progress. Ever since then I usually get one of those http errors, perhaps a time-out of sorts due to the slowness caused by the debug channels wide open. I also did a quick comparison of 'mshtml' logs, and I did notice something somewhat curious: there are a bunch of 'nulls' when running with vanilla Wine: 0130:trace:mshtml:DispatchEx_AddRef (null) (0000000001D21818) ref=2 0130:trace:mshtml:DispatchEx_AddRef (null) (00000000020F32D0) ref=2 With Valve Wine they get: 0140:trace:mshtml:DispatchEx_AddRef Window (0000000008454A90) ref=2 0140:trace:mshtml:DispatchEx_AddRef HTMLDocument (00000000087C6DC0) ref=2 There are also differences such as the following: 0130:trace:mshtml:DispatchEx_AddRef Document (000000000276DD00) ref=6 0130:trace:mshtml:DispatchEx_AddRef Document (000000000276DD00) ref=7 VS 0140:trace:mshtml:DispatchEx_AddRef HTMLDocument (00000000093CEC50) ref=6 0140:trace:mshtml:DispatchEx_AddRef HTMLDocument (00000000093CEC50) ref=7 I suppose these probably mean nothing for the stuckiness, but I figured I'd at least mention them. -- 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.