https://bugs.winehq.org/show_bug.cgi?id=55469
Bug ID: 55469 Summary: GL_OUT_OF_MEMORY crash Product: Wine Version: 8.14 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: wschmrdr@gmail.com Distribution: ---
Starting with Wine 8.14, after playing just a second co-op game, I receive a "GL_OUT_OF_MEMORY" error, followed by several instances of "Cannot allocate memory", followed by the typical "RtlpWaitForCriticalSection" crash I have also experienced in previous versions if I play too many matches. Not sure if the two are related, but with previous versions (up to 8.13), I was able to play a couple matches and then restart the application as a sort of workaround.
https://bugs.winehq.org/show_bug.cgi?id=55469
--- Comment #1 from Rafał Mużyło galtgendo@o2.pl --- ...:sigh:...
*Which* game ?
Also, recheck if 8.13 actually did work better - one version difference is quite narrow, which is nice (only specific commits are better).
https://bugs.winehq.org/show_bug.cgi?id=55469
--- Comment #2 from wschmrdr@gmail.com --- My apologies, as I came from the Starcraft II listing to put this in; this is for Starcraft II. As for 8.13, I did revert to that version, and am not seeing the memory issues in the middle of game 1 or 2; was playing co-op mode.
https://bugs.winehq.org/show_bug.cgi?id=55469
--- Comment #3 from Rafał Mużyło galtgendo@o2.pl --- Attach the full console output leading to the crash.
Is that a 32bit or 64bit executable ? ...the later would be quite odd...
https://bugs.winehq.org/show_bug.cgi?id=55469
--- Comment #4 from wschmrdr@gmail.com --- Created attachment 75119 --> https://bugs.winehq.org/attachment.cgi?id=75119 Error Log seen
Upgraded to 8.15, and although we're back to the same timing for the memory issue as 8.13, I'm still receiving it, albeit with a little more detail that was included in 8.14 but not 8.13. I've attached the terminal output that shows the error being received. I am running the 64-bit client.
https://bugs.winehq.org/show_bug.cgi?id=55469
--- Comment #5 from wschmrdr@gmail.com --- Upgraded to 8.15, still seeing the issue but at the same frequency as 8.13. Added an attachment with what's coming out of the terminal; please advise if there's some other log file that should be generated, and where it can be found.
https://bugs.winehq.org/show_bug.cgi?id=55469
--- Comment #6 from Rafał Mużyło galtgendo@o2.pl --- Well, that roughly the output that was asked for or rather the tail end of it.
Would be better if it started at least a little bit before first GL_OUT_OF_MEMORY, even though the chances are it won't say anything of real use cause the problem likely lies deeper in the memory allocations for video processing.
Though, are you sure the final executable (not the launcher or whatever) is 64bit ?
https://bugs.winehq.org/show_bug.cgi?id=55469
--- Comment #7 from wschmrdr@gmail.com --- The log does have the typical spamming of:
00e8:fixme:sync:NtQueryDirectoryObject multiple entries not implemented
...just before the log output. However, I do see a couple isolated incidents of the following:
0184:err:virtual:map_view anon mmap error Cannot allocate memory, size 0x20020000, unix_prot 0 0184:err:virtual:allocate_virtual_memory out of memory for allocation, base (nil) size 20010000 0184:err:d3d:buffer_invalidate_bo_range Failed to allocate maps array, invalidating entire buffer.
It happens once, but still performs OK.
As for whether I'm running 32 or 64, I am basing this when I go into the launcher, the game settings, and see that running the 32-bit version is unchecked. Looking at my packages, I have both wine-devel-amd64 and wine-devel-i386:i386 installed. However, be aware, when I run SC2, unless I get kicked out for not having an update, I run from the terminal using:
wine C:\Program\ Files\ (x86)\StarCraft\ II\Support\SC2Switcher.exe
I also see that WINE 8.16 has come out; I'll give it an upgrade, and then when I have a chance to try it out again, I'll give it a shot.
https://bugs.winehq.org/show_bug.cgi?id=55469
--- Comment #8 from wschmrdr@gmail.com --- Just tried it with 8.16, and only able to get through one match before seeing the same error previously included in the log. Since it looks to be related to wined3d, here are a few more outputs related to that I'm seeing in my log; note they will be snippets because of all the spam of the same message surrounding these:
00dc:fixme:d3d:wined3d_check_device_format_conversion output 07932510, device_type WINED3D_DEVICE_TYPE_HAL, src_format WINED3DFMT_B8G8R8A8_UNORM, dst_format WINED3DFMT_B8G8R8X8_UNORM stub! 00dc:fixme:d3d:debug_d3dformat Unrecognized 0x36314644 (as fourcc: DF16) WINED3DFORMAT! 00dc:fixme:d3d:wined3d_get_format Can't find format unrecognized (0x36314644) in the format lookup table. 00dc:fixme:d3d:debug_d3dformat Unrecognized 0x36314644 (as fourcc: DF16) WINED3DFORMAT! 00dc:fixme:d3d:wined3d_get_format Can't find format unrecognized (0x36314644) in the format lookup table. 00dc:fixme:d3d:debug_d3dformat Unrecognized 0x34324644 (as fourcc: DF24) WINED3DFORMAT! 00dc:fixme:d3d:wined3d_get_format Can't find format unrecognized (0x34324644) in the format lookup table. 00dc:fixme:d3d:debug_d3dformat Unrecognized 0x34324644 (as fourcc: DF24) WINED3DFORMAT! 00dc:fixme:d3d:wined3d_get_format Can't find format unrecognized (0x34324644) in the format lookup table.
....
00dc:fixme:wbemprox:client_security_SetBlanket 16B41850, 079E4E30, 10, 0, (null), 3, 3, 00000000, 0 00dc:fixme:wbemprox:client_security_Release 16B41850 0058:fixme:nsi:ipv6_forward_enumerate_all not implemented 00dc:fixme:d3d:wined3d_check_device_format_conversion output 07932510, device_type WINED3D_DEVICE_TYPE_HAL, src_format WINED3DFMT_B8G8R8A8_UNORM, dst_format WINED3DFMT_B8G8R8X8_UNORM stub! 0178:fixme:d3d:state_linepattern_w Setting line patterns is not supported in OpenGL core contexts. 00dc:fixme:sync:NtQueryDirectoryObject multiple entries not implemented 01d8:fixme:winsock:WSAIoctl SIO_UDP_CONNRESET stub 00dc:fixme:sync:NtQueryDirectoryObject multiple entries not implemented
...
00dc:fixme:sync:NtQueryDirectoryObject multiple entries not implemented 0178:err:virtual:map_view anon mmap error Cannot allocate memory, size 0x10020000, unix_prot 0 0178:err:virtual:allocate_virtual_memory out of memory for allocation, base (nil) size 10010000 0178:err:d3d:buffer_invalidate_bo_range Failed to allocate maps array, invalidating entire buffer. 00dc:fixme:sync:NtQueryDirectoryObject multiple entries not implemented
https://bugs.winehq.org/show_bug.cgi?id=55469
Olivier F. R. Dierick o.dierick@piezo-forte.be changed:
What |Removed |Added ---------------------------------------------------------------------------- Summary|GL_OUT_OF_MEMORY crash |Starcraft II | |GL_OUT_OF_MEMORY crash CC| |o.dierick@piezo-forte.be
https://bugs.winehq.org/show_bug.cgi?id=55469
Zeb Figura z.figura12@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |DUPLICATE Regression SHA1| |c065b4fe0b3622e0c737a4c7c1c | |514273ad2d8a7 CC| |z.figura12@gmail.com Component|-unknown |d3d Keywords| |regression Status|UNCONFIRMED |RESOLVED
--- Comment #9 from Zeb Figura z.figura12@gmail.com --- This is the same cause as bug 55654.
*** This bug has been marked as a duplicate of bug 55654 ***
https://bugs.winehq.org/show_bug.cgi?id=55469
Gijs Vermeulen gijsvrm@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #10 from Gijs Vermeulen gijsvrm@gmail.com --- Closing.
-
WineHQ Bugzilla