On Tue Oct 18 21:43:53 2022 +0000, Alexandre Julliard wrote:
> > The first one seems to be caused by an OOM error. I've seen similar
> issues in the past when running the tests under llvmpipe, and when
> multiple D3D devices are initialized. The llvmpipe GL context is memory
> hungry and it quickly fills the 32-bit address space.
> >
> > This doesn't disculp this changes in any way and it could be very well
> related, if for some reason the messages here are causing GL contexts to
> be re-created more often or at different times.
> It's possible that the failures could have been triggered before, though
> I don't remember ever seeing the d3drm one.
> But they are happening much more often, almost every test run has one of
> them now. We need to fix that.
Yes, I'm investigating. I can reproduce the failures locally, and they look indeed related.
--
https://gitlab.winehq.org/wine/wine/-/merge_requests/944#note_11205
> The first one seems to be caused by an OOM error. I've seen similar issues in the past when running the tests under llvmpipe, and when multiple D3D devices are initialized. The llvmpipe GL context is memory hungry and it quickly fills the 32-bit address space.
>
> This doesn't disculp this changes in any way and it could be very well related, if for some reason the messages here are causing GL contexts to be re-created more often or at different times.
It's possible that the failures could have been triggered before, though I don't remember ever seeing the d3drm one.
But they are happening much more often, almost every test run has one of them now. We need to fix that.
--
https://gitlab.winehq.org/wine/wine/-/merge_requests/944#note_11204
--
v3: vkd3d-shader/hlsl: Parse UAV types.
vkd3d-shader/hlsl: Parse texture index expressions.
vkd3d-shader/hlsl: Cast array indices inside of add_array_load().
tests: Add a basic shader test for typed UAV loads.
tests: Add a basic shader test for compute shaders.
https://gitlab.winehq.org/wine/vkd3d/-/merge_requests/30
On Tue Oct 18 17:24:25 2022 +0000, Alexandre Julliard wrote:
> I have a feeling that the recent stream of ddraw and d3drm test failures
> are also related to this MR. Any ideas?
Do you mean the `d3drm.c:4776: Test failed: Cannot create IDirect3DRMDevice2 interface, hr 0x8007000e.` and the `ddraw7.c:15663: Test failed: Expected unsynchronised map for flags 0x1000.` kind of errors?
The first one seems to be caused by an OOM error. I've seen similar issues in the past when running the tests under llvmpipe, and when multiple D3D devices are initialized. The llvmpipe GL context is memory hungry and it quickly fills the 32-bit address space.
This doesn't disculp this changes in any way and it could be very well related, if for some reason the messages here are causing GL contexts to be re-created more often or at different times.
For the ddraw issue, I can't guess where it comes from, I believe I've seen the errors before but I'll have to investigate. I'll probably need to re-create the test environment to be sure, these tests tend to be annoying to run as they changes the display modes.
--
https://gitlab.winehq.org/wine/wine/-/merge_requests/944#note_11182
This series improves support for blocks which spread across several
non contiguous memory chunks.
Mingw/Gcc tends to emit quite a few of these, especially in 32bit mode.
Now the gaps (between two valid ranges) will no longer be understood
as being part of the block, hence potentially hiding valid information
lying in other blocks.
Note that native doesn't support blocks with multiple ranges of addresses
(MSVC stores the information quite differently), so these ranges will
be used internally but not exposed to DbgHelp's user.
--
https://gitlab.winehq.org/wine/wine/-/merge_requests/1091
--
v2: comctl32: Add helper for getting icon from HPROPSHEETPAGE.
comctl32: Add helper for getting title from HPROPSHEETPAGE.
comctl32: Add helper for loading dialog template from HPROPSHEETPAGE.
https://gitlab.winehq.org/wine/wine/-/merge_requests/1072