New subject: [Bug 54747] ddraw:dsurface sometimes gets E_OUTOFMEMORY on Windows

28 Mar 2023


      https://bugs.winehq.org/show_bug.cgi?id=54747
Bug ID: 54747
           Summary: ddraw:dsurface sometimes gets E_OUTOFMEMORY on Windows
           Product: Wine
           Version: unspecified
          Hardware: x86-64
                OS: Windows
            Status: NEW
          Severity: normal
          Priority: P2
         Component: d3d
          Assignee: wine-bugs@winehq.org
          Reporter: fgouget@codeweavers.com
ddraw:dsurface sometimes gets E_OUTOFMEMORY on Windows. However this does not
always happen in the same place:
* 2022-08-31 in test_ddsd() on w1064-tsign-64:
  dsurface.c:2232: Test failed: Got hr 0x8007000e.
* 2022-10-14 in BackBufferAttachmentFlipTest() on w1064-tsign-32:
  dsurface.c:1710: Test failed: Got hr 0x8007000e.
  dsurface.c:1758: Test failed: Attaching a back buffer to another back buffer
returned 0x80070057
  dsurface.c:1776: this is the last test seen before the exception
  14a8:dsurface: unhandled exception c0000005 at 00553E4A
* 2022-12-09 in PaletteTest(), BackBufferAttachmentFlipTest() and test_ddsd()
on w1064-tsign-64:
  dsurface.c:1372: Test failed: Got hr 0x8007000e.
  dsurface.c:1375: Tests skipped: failed to create surface
  dsurface.c:1691: Test failed: Got hr 0x8007000e.
  dsurface.c:2232: Test failed: Got hr 0x8007000e.
* 2023-01-24 in BackBufferAttachmentFlipTest() and zbufferbitdepth_test() on
w10pro64-fr-64:
  dsurface.c:1691: Test failed: Got hr 0x8007000e.
  dsurface.c:2130: Test failed: Got hr 0x8007000e.
  dsurface.c:2130: this is the last test seen before the exception
  1f40:dsurface: unhandled exception c0000005 at 0000000000522CD1
* 2023-03-27 in test_ddsd() on w10pro64-ru-64
  dsurface.c:2232: Test failed: Got hr 0x8007000e.
See https://test.winehq.org/data/patterns.html#ddraw:dsurface
Where 0x8007000e == E_OUTOFMEMORY
Notes:
* There are really 5 places where this happens.
* It always happens after a IDirectDraw_CreateSurface() call, except for the
test_ddsd() (line 2232) cases where it follows a IDirectDrawSurface7_Lock()
call.
* The failure dates look somewhat similar to the ddraw:ddrawmodes E_OUTOFMEMORY
failures but not exactly and the VMs mostly don't match. So the ddrawmodes
failures are not the cause of the dsurface ones. But there may be some common
factor making these failures more likely.
-- 
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.

[Bug 54747] New: ddraw:dsurface sometimes gets E_OUTOFMEMORY on Windows