https://bugs.winehq.org/show_bug.cgi?id=40477
--- Comment #3 from Józef Kucia joseph.kucia@gmail.com --- (In reply to Wylda from comment #0)
This commit fixed bug 39878. Despite it should limit the mem, i see some suspicious lines like:
trace:d3d:resource_cleanup Decrementing device memory pool by 9216000 trace:d3d:adapter_adjust_memory Adjusted used adapter memory by 0xffffffffff736000 to 0x0.
These are normal.
This issue was present before the mentioned commit for some GPUs. Motorcross Madness calls ddraw7_GetAvailableVidMem() at start and when it doesn't like the returned values it exits. The game happened to work for you by accident because it works when the reported amount of memory is 0xffffffff. It stopped to work now because the reported amount is now limited to 0x7fffffff. In any case, the game wasn't working with 2GB GPUs before the commit 565a5715468fa990cf9e7cbfe38ac59ddcde1e76.
I haven't debugged in which exact way the video memory size detection is broken in Motorcross Madness so I don't know the exact conditions the reported amount of memory have to meet but it seems that we could potentially use a little smaller value than LONG_MAX as a memory limit to make Motorcross Madness and Diablo 2 happy.