https://bugs.winehq.org/show_bug.cgi?id=53107 --- Comment #2 from fallenguru(a)protonmail.com --- (In reply to Rafał Mużyło from comment #1) Thanks for looking at this!
'Failed to allocate system memory.' might actually mean 'run out of virtual mapping space'.
I thought it might. (But then I also thought WINE_LARGE_ADDRESS_AWARE help with that?)
Check VmPeak/VmSize of the process' /proc status file while process is running.
This is a couple of sec after the crash (without WINE_LARGE_ADDRESS_AWARE): VmPeak: 4154728 kB VmSize: 4154664 kB For reference, this is after launch, just sitting at the main menu: VmPeak: 3907360 kB VmSize: 3637476 kB Wouldn't take much to hit a 4 GB wall. The point is, Windows doesn't, and neither does DXVK. w/ DXVK, main menu: VmPeak: 3891012 kB VmSize: 3349860 kB w/ DXVK, effect playing: VmPeak: 3946008 kB VmSize: 3945848 kB w/ DXVK, on the first screen after the effect. VmPeak: 3946008 kB VmSize: 3716472 kB -- 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.