https://bugs.winehq.org/show_bug.cgi?id=53235
Giovanni Mascellani gmascellani@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |gmascellani@codeweavers.com
--- Comment #1 from Giovanni Mascellani gmascellani@codeweavers.com --- This seems to be an unhandled memory allocation failure:
01f8:err:d3d:wined3d_debug_callback 001AFFA8: "GL_OUT_OF_MEMORY in glBufferStorage". 01f8:err:d3d:wined3d_debug_callback 001AFFA8: "GL_INVALID_VALUE in glMapBufferRange(offset 0 + length 67108864 > buffer_size 0)". 01f8:err:d3d:wined3d_allocator_chunk_gl_map Failed to map chunk memory. 01f8:err:d3d:wined3d_bo_gl_map Failed to map chunk. 01f8:err:d3d:wined3d_context_gl_map_bo_address Failed to map bo. wine: Unhandled page fault on write access to 00000000 at address 70BAFD94 (thread 01f8), starting debugger...
BTW, on the testbot running with +d3d gives:
00f8:trace:d3d:wined3d_adapter_init_gl_caps GL_RENDERER: "llvmpipe (LLVM 11.0.1, 256 bits)". 00f8:trace:d3d:wined3d_adapter_init_gl_caps GL_VENDOR: "Mesa/X.org". 00f8:trace:d3d:wined3d_adapter_init_gl_caps GL_VERSION: "4.5 (Core Profile) Mesa 20.3.5".
While on my computer (using "LIBGL_ALWAYS_SOFTWARE=1 GALLIUM_DRIVER=llvmpipe" to force llvmpipe) I get:
0024:trace:d3d:4P:714CB0E3:ine/dlls/wined3d/adapter_gl.c:3413:wined3d_adapter_init_gl_caps GL_RENDERER: "llvmpipe (LLVM 14.0.4, 256 bits)". 0024:trace:d3d:4P:714CB0E3:ine/dlls/wined3d/adapter_gl.c:3421:wined3d_adapter_init_gl_caps GL_VENDOR: "Mesa/X.org". 0024:trace:d3d:4P:714CB0E3:ine/dlls/wined3d/adapter_gl.c:3430:wined3d_adapter_init_gl_caps GL_VERSION: "4.5 (Core Profile) Mesa 22.0.5".
So it might be a bug that was fixed between Mesa 20.3.5 and Mesa 22.0.5. In theory Wine should gracefully handle the failed allocation anyway.