http://bugs.winehq.org/show_bug.cgi?id=59333 --- Comment #23 from Madalee <madalee@ohlmeyers.com> --- We forked GE-Proton and Kron4ek Wine-Builds, then took the changes that Hoshino Lina pointed to, and reverted those changes in to Proton 10 - Wine. We've got a build of GE-Proton with those changes that we're testing now. If any of you have a better way to repeat the issue, like Adalyn, you can test this: https://github.com/madalee-com/proton-ge-custom-unity-leak-fix For GE-Proton we applied the change after the source code gets pulled and before any of the patches are applied. Not sure if these changes make their way through to the final build or not. None-the-less, testing it. For Kron4ek/Wine-Builds, this one is way more clean. We put the changes in place between the git clone and the build. Pretty sure that one should be a valid test. It's building now, though it wont be available for several hours. This one will be available in build artifacts here, if you have a logged in github account, we think. If not, we'll put it in a release for others to test: https://github.com/madalee-com/Wine-Builds-fix-unity-leak/actions/runs/22272... If you want to take a look at how we reverted the changes, here is the specific file we changed. This is pulled from Proton-10/wine branch and the reverted code was from Proton-8/wine branch. https://github.com/madalee-com/Wine-Builds-fix-unity-leak/blob/master/signal... -- 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.