https://bugs.winehq.org/show_bug.cgi?id=54833
--- Comment #9 from Zeb Figura z.figura12@gmail.com --- (In reply to Rafał Mużyło from comment #7)
0120:err:d3d:wined3d_debug_callback 0124E308: "GL_OUT_OF_MEMORY error generated. Failed to allocate CPU address space mapping for buffer object (consider building 64-bit app).".
That's one of the nasty ones - some apps/games map excessively in wine. Some even far above what you'd expect from game size (IIRC I've seen below 1G in size games dying from this). It's relatively rare and would be nice if it got fixed, but chances are it won't be.
It doesn't necessarily have to do with applications performing 3D mappings, or even if it does, that's an odd thing to ascribe blame to, seeing as those mappings happen on Windows as well and the latter usually does fine. More likely culprits include excessively sized system libraries, PulseAudio shared memory slices, or system 3D drivers not unmapping buffers even when we ask them to.
Perhaps once the new 32-on-64 mode becomes reliable things get changed, but that's not a given.
New-style wow64 won't help most of this, at least not by itself. Mappings accessible to the PE side still need to go in the bottom 2 (or 4) GiB.
If you checked the range correctly, Zeb is most likely the author of the change that triggered this.
What change?
(In reply to Rafał Mużyło from comment #8)
...PS: perhaps there's another gotcha about 831ff102008e2ba93a403344646b5ed67258eaeb...
In what way?