https://bugs.winehq.org/show_bug.cgi?id=46568
--- Comment #4 from Paul Gofman gofmanp@gmail.com --- (In reply to Louis Lenders from comment #3)
(In reply to Paul Gofman from comment #2)
is this now a duplicate or should it be linked to the AION-bug?
This does not look a duplicate to me, though solution I want to test is supposed to help both (and that's how this version of msxml and probably Mortal Kombat 11 succeed on Windows 8+). Here the program relies on pre-Win8 16TB user space address limit, which was lifted in Win8. AION is not fine with 8TB address range, it wants the addresses in 16GB range in my observations. All of that succeed on Windows (most of the time) because Windows allocates virtual memory bottom up (unless top down is explicitly requested for virtual allocation). That is, it will not give an application high memory pointers if the lower memory addresses are available. My patch makes Wine allocations behave in a similar way.