http://bugs.winehq.org/show_bug.cgi?id=59771 --- Comment #5 from fumadordeducados@gmail.com --- Further testing: A fresh installation on a clean win64 WINEPREFIX with no prior tracking data starts correctly after letting it run a bit longer. It seems that the bug is triggered by existing user data. The original setup used a "portable" mode (empty file named portable in the installation directory), which causes TrackChecker to store its data locally rather than in AppData. This includes data.xml (~3.4MB, containing hundreds of accumulated tracking entries) Copying only data.xml (~3.4MB, containing hundreds of accumulated tracking entries) into a fresh portable-mode installation reproduces the bug immediately. The three domdoc_get_parseError semi-stub calls become six (two DOMDocument objects being parsed), then the process enters 100% CPU infinite recursion. Without data.xml (fresh install, no data): starts correctly. With data.xml present: hangs at ~100% CPU, no window. The root cause is likely specific content or structure in data.xml that triggers a code path in Wine 11.7+'s new MSXML reimplementation that was handled correctly in Wine 11.6. -- 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.