This works fine currently, but won't once we start suballocating GL buffers.
Signed-off-by: Zebediah Figura zfigura@codeweavers.com --- This is a bit of a sledgehammer solution (and actually d2d1 and d3d10core at least seem to be fine with just limiting the thread count to 4). We could instead use separate processes, but it doesn't seem particularly worthwhile to write that code when we might end up being limited by VRAM anyway.
dlls/d2d1/tests/d2d1.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/dlls/d2d1/tests/d2d1.c b/dlls/d2d1/tests/d2d1.c index 6bc6a99274c..d0fee842ed5 100644 --- a/dlls/d2d1/tests/d2d1.c +++ b/dlls/d2d1/tests/d2d1.c @@ -161,7 +161,9 @@ static void run_queued_tests(void) SYSTEM_INFO si; LONG test_idx;
- if (!use_mt) + /* Running the tests multithreaded on 32-bit maps too much memory in Wine, + * even with only 2 threads. */ + if (!use_mt || sizeof(void *) == 4) { for (i = 0; i < mt_test_count; ++i) {
This works fine currently, but won't once we start suballocating GL buffers.
Signed-off-by: Zebediah Figura zfigura@codeweavers.com --- dlls/d3d10core/tests/d3d10core.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/dlls/d3d10core/tests/d3d10core.c b/dlls/d3d10core/tests/d3d10core.c index e2a4be67d66..0fcaf041187 100644 --- a/dlls/d3d10core/tests/d3d10core.c +++ b/dlls/d3d10core/tests/d3d10core.c @@ -129,7 +129,9 @@ static void run_queued_tests(void) SYSTEM_INFO si; LONG test_idx;
- if (!use_mt) + /* Running the tests multithreaded on 32-bit maps too much memory in Wine, + * even with only 2 threads. */ + if (!use_mt || sizeof(void *) == 4) { for (i = 0; i < mt_test_count; ++i) {
Hi,
While running your changed tests, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check?
Full results can be found at: https://testbot.winehq.org/JobDetails.pl?Key=106963
Your paranoid android.
=== w1064v1809 (64 bit report) ===
d3d10core: d3d10core.c:4782: Test failed: Got unexpected IAVertices count: 0. d3d10core.c:4783: Test failed: Got unexpected IAPrimitives count: 0. d3d10core.c:4784: Test failed: Got unexpected VSInvocations count: 0. d3d10core.c:4787: Test failed: Got unexpected CInvocations count: 0. d3d10core.c:4788: Test failed: Got unexpected CPrimitives count: 0.
This works fine currently, but won't once we start suballocating GL buffers.
Signed-off-by: Zebediah Figura zfigura@codeweavers.com --- dlls/d3d11/tests/d3d11.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/dlls/d3d11/tests/d3d11.c b/dlls/d3d11/tests/d3d11.c index 72324063130..5ed58d5f182 100644 --- a/dlls/d3d11/tests/d3d11.c +++ b/dlls/d3d11/tests/d3d11.c @@ -201,7 +201,9 @@ static void run_queued_tests(void) SYSTEM_INFO si; LONG test_idx;
- if (!use_mt) + /* Running the tests multithreaded on 32-bit maps too much memory in Wine, + * even with only 2 threads. */ + if (!use_mt || sizeof(void *) == 4) { for (i = 0; i < mt_test_count; ++i) {
Hi,
While running your changed tests, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check?
Full results can be found at: https://testbot.winehq.org/JobDetails.pl?Key=106964
Your paranoid android.
=== w1064v1809 (32 bit report) ===
d3d11: d3d11.c:5807: Test failed: Got unexpected query result 0x0000000000000000.
=== debian11 (32 bit report) ===
d3d11: d3d11.c:28278: Test failed: Got texcoord {8.43750119e-001, 1.56249881e-001}, expected {8.43750000e-001, 1.56250000e-001} at (3, 3), offset 1.25000000e-001. d3d11.c:28278: Test failed: Got texcoord {8.71093690e-001, 1.28906310e-001}, expected {8.71093750e-001, 1.28906250e-001} at (3, 3), offset 1.56250000e-002. d3d11.c:28278: Test failed: Got texcoord {7.51953065e-001, 2.48046935e-001}, expected {7.51953125e-001, 2.48046875e-001} at (3, 3), offset 4.92187500e-001. d3d11.c:28332: Test succeeded inside todo block: Got 0xffffffff, expected 0xffffffff at (640, 480, 1), sub-resource 0. d3d11.c:28341: Test succeeded inside todo block: Got 0xffffffff, expected 0xffffffff at (640, 480, 1), sub-resource 0. d3d11.c:28332: Test failed: Got 0xffffffff, expected 0xff00ff00 at (639, 479, 0), sub-resource 0. d3d11.c:28341: Test failed: Got 0xffffffff, expected 0xff00ff00 at (639, 479, 0), sub-resource 0. d3d11.c:28332: Test failed: Got 0xffffffff, expected 0xff00ff00 at (639, 479, 0), sub-resource 0. d3d11.c:28341: Test failed: Got 0xffffffff, expected 0xff00ff00 at (639, 479, 0), sub-resource 0.
=== debian11 (32 bit Arabic:Morocco report) ===
d3d11: d3d11.c:28278: Test failed: Got texcoord {8.43750119e-001, 1.56249881e-001}, expected {8.43750000e-001, 1.56250000e-001} at (3, 3), offset 1.25000000e-001. d3d11.c:28278: Test failed: Got texcoord {8.71093690e-001, 1.28906310e-001}, expected {8.71093750e-001, 1.28906250e-001} at (3, 3), offset 1.56250000e-002. d3d11.c:28278: Test failed: Got texcoord {7.51953065e-001, 2.48046935e-001}, expected {7.51953125e-001, 2.48046875e-001} at (3, 3), offset 4.92187500e-001. d3d11.c:28332: Test succeeded inside todo block: Got 0xffffffff, expected 0xffffffff at (640, 480, 1), sub-resource 0. d3d11.c:28341: Test succeeded inside todo block: Got 0xffffffff, expected 0xffffffff at (640, 480, 1), sub-resource 0. d3d11.c:28332: Test failed: Got 0xffffffff, expected 0xff00ff00 at (639, 479, 0), sub-resource 0. d3d11.c:28341: Test failed: Got 0xffffffff, expected 0xff00ff00 at (639, 479, 0), sub-resource 0. d3d11.c:28332: Test failed: Got 0xffffffff, expected 0xff00ff00 at (639, 479, 0), sub-resource 0. d3d11.c:28341: Test failed: Got 0xffffffff, expected 0xff00ff00 at (639, 479, 0), sub-resource 0.
=== debian11 (32 bit German report) ===
d3d11: d3d11.c:28278: Test failed: Got texcoord {8.43750119e-001, 1.56249881e-001}, expected {8.43750000e-001, 1.56250000e-001} at (3, 3), offset 1.25000000e-001. d3d11.c:28278: Test failed: Got texcoord {8.71093690e-001, 1.28906310e-001}, expected {8.71093750e-001, 1.28906250e-001} at (3, 3), offset 1.56250000e-002. d3d11.c:28278: Test failed: Got texcoord {7.51953065e-001, 2.48046935e-001}, expected {7.51953125e-001, 2.48046875e-001} at (3, 3), offset 4.92187500e-001. d3d11.c:28332: Test succeeded inside todo block: Got 0xffffffff, expected 0xffffffff at (640, 480, 1), sub-resource 0. d3d11.c:28341: Test succeeded inside todo block: Got 0xffffffff, expected 0xffffffff at (640, 480, 1), sub-resource 0. d3d11.c:28332: Test failed: Got 0xffffffff, expected 0xff00ff00 at (639, 479, 0), sub-resource 0. d3d11.c:28341: Test failed: Got 0xffffffff, expected 0xff00ff00 at (639, 479, 0), sub-resource 0. d3d11.c:28332: Test failed: Got 0xffffffff, expected 0xff00ff00 at (639, 479, 0), sub-resource 0. d3d11.c:28341: Test failed: Got 0xffffffff, expected 0xff00ff00 at (639, 479, 0), sub-resource 0.
=== debian11 (32 bit French report) ===
d3d11: d3d11.c:28278: Test failed: Got texcoord {8.43750119e-001, 1.56249881e-001}, expected {8.43750000e-001, 1.56250000e-001} at (3, 3), offset 1.25000000e-001. d3d11.c:28278: Test failed: Got texcoord {8.71093690e-001, 1.28906310e-001}, expected {8.71093750e-001, 1.28906250e-001} at (3, 3), offset 1.56250000e-002. d3d11.c:28278: Test failed: Got texcoord {7.51953065e-001, 2.48046935e-001}, expected {7.51953125e-001, 2.48046875e-001} at (3, 3), offset 4.92187500e-001. d3d11.c:28332: Test succeeded inside todo block: Got 0xffffffff, expected 0xffffffff at (640, 480, 1), sub-resource 0. d3d11.c:28341: Test succeeded inside todo block: Got 0xffffffff, expected 0xffffffff at (640, 480, 1), sub-resource 0. d3d11.c:28332: Test failed: Got 0xffffffff, expected 0xff00ff00 at (639, 479, 0), sub-resource 0. d3d11.c:28341: Test failed: Got 0xffffffff, expected 0xff00ff00 at (639, 479, 0), sub-resource 0. d3d11.c:28332: Test failed: Got 0xffffffff, expected 0xff00ff00 at (639, 479, 0), sub-resource 0. d3d11.c:28341: Test failed: Got 0xffffffff, expected 0xff00ff00 at (639, 479, 0), sub-resource 0.
=== debian11 (32 bit Hebrew:Israel report) ===
d3d11: d3d11.c:28278: Test failed: Got texcoord {8.43750119e-001, 1.56249881e-001}, expected {8.43750000e-001, 1.56250000e-001} at (3, 3), offset 1.25000000e-001. d3d11.c:28278: Test failed: Got texcoord {8.71093690e-001, 1.28906310e-001}, expected {8.71093750e-001, 1.28906250e-001} at (3, 3), offset 1.56250000e-002. d3d11.c:28278: Test failed: Got texcoord {7.51953065e-001, 2.48046935e-001}, expected {7.51953125e-001, 2.48046875e-001} at (3, 3), offset 4.92187500e-001. d3d11.c:28332: Test succeeded inside todo block: Got 0xffffffff, expected 0xffffffff at (640, 480, 1), sub-resource 0. d3d11.c:28341: Test succeeded inside todo block: Got 0xffffffff, expected 0xffffffff at (640, 480, 1), sub-resource 0. d3d11.c:28332: Test failed: Got 0xffffffff, expected 0xff00ff00 at (639, 479, 0), sub-resource 0. d3d11.c:28341: Test failed: Got 0xffffffff, expected 0xff00ff00 at (639, 479, 0), sub-resource 0. d3d11.c:28332: Test failed: Got 0xffffffff, expected 0xff00ff00 at (639, 479, 0), sub-resource 0. d3d11.c:28341: Test failed: Got 0xffffffff, expected 0xff00ff00 at (639, 479, 0), sub-resource 0.
=== debian11 (32 bit Hindi:India report) ===
d3d11: d3d11.c:28278: Test failed: Got texcoord {8.43750119e-001, 1.56249881e-001}, expected {8.43750000e-001, 1.56250000e-001} at (3, 3), offset 1.25000000e-001. d3d11.c:28278: Test failed: Got texcoord {8.71093690e-001, 1.28906310e-001}, expected {8.71093750e-001, 1.28906250e-001} at (3, 3), offset 1.56250000e-002. d3d11.c:28278: Test failed: Got texcoord {7.51953065e-001, 2.48046935e-001}, expected {7.51953125e-001, 2.48046875e-001} at (3, 3), offset 4.92187500e-001. d3d11.c:28332: Test succeeded inside todo block: Got 0xffffffff, expected 0xffffffff at (640, 480, 1), sub-resource 0. d3d11.c:28341: Test succeeded inside todo block: Got 0xffffffff, expected 0xffffffff at (640, 480, 1), sub-resource 0. d3d11.c:28332: Test failed: Got 0xffffffff, expected 0xff00ff00 at (639, 479, 0), sub-resource 0. d3d11.c:28341: Test failed: Got 0xffffffff, expected 0xff00ff00 at (639, 479, 0), sub-resource 0. d3d11.c:28332: Test failed: Got 0xffffffff, expected 0xff00ff00 at (639, 479, 0), sub-resource 0. d3d11.c:28341: Test failed: Got 0xffffffff, expected 0xff00ff00 at (639, 479, 0), sub-resource 0.
=== debian11 (32 bit Japanese:Japan report) ===
d3d11: d3d11.c:28278: Test failed: Got texcoord {8.43750119e-001, 1.56249881e-001}, expected {8.43750000e-001, 1.56250000e-001} at (3, 3), offset 1.25000000e-001. d3d11.c:28278: Test failed: Got texcoord {8.71093690e-001, 1.28906310e-001}, expected {8.71093750e-001, 1.28906250e-001} at (3, 3), offset 1.56250000e-002. d3d11.c:28278: Test failed: Got texcoord {7.51953065e-001, 2.48046935e-001}, expected {7.51953125e-001, 2.48046875e-001} at (3, 3), offset 4.92187500e-001. d3d11.c:28332: Test succeeded inside todo block: Got 0xffffffff, expected 0xffffffff at (640, 480, 1), sub-resource 0. d3d11.c:28341: Test succeeded inside todo block: Got 0xffffffff, expected 0xffffffff at (640, 480, 1), sub-resource 0. d3d11.c:28332: Test failed: Got 0xffffffff, expected 0xff00ff00 at (639, 479, 0), sub-resource 0. d3d11.c:28341: Test failed: Got 0xffffffff, expected 0xff00ff00 at (639, 479, 0), sub-resource 0. d3d11.c:28332: Test failed: Got 0xffffffff, expected 0xff00ff00 at (639, 479, 0), sub-resource 0. d3d11.c:28341: Test failed: Got 0xffffffff, expected 0xff00ff00 at (639, 479, 0), sub-resource 0.
=== debian11 (32 bit Chinese:China report) ===
d3d11: d3d11.c:28278: Test failed: Got texcoord {8.43750119e-001, 1.56249881e-001}, expected {8.43750000e-001, 1.56250000e-001} at (3, 3), offset 1.25000000e-001. d3d11.c:28278: Test failed: Got texcoord {8.71093690e-001, 1.28906310e-001}, expected {8.71093750e-001, 1.28906250e-001} at (3, 3), offset 1.56250000e-002. d3d11.c:28278: Test failed: Got texcoord {7.51953065e-001, 2.48046935e-001}, expected {7.51953125e-001, 2.48046875e-001} at (3, 3), offset 4.92187500e-001. d3d11.c:28332: Test succeeded inside todo block: Got 0xffffffff, expected 0xffffffff at (640, 480, 1), sub-resource 0. d3d11.c:28341: Test succeeded inside todo block: Got 0xffffffff, expected 0xffffffff at (640, 480, 1), sub-resource 0. d3d11.c:28332: Test failed: Got 0xffffffff, expected 0xff00ff00 at (639, 479, 0), sub-resource 0. d3d11.c:28341: Test failed: Got 0xffffffff, expected 0xff00ff00 at (639, 479, 0), sub-resource 0. d3d11.c:28332: Test failed: Got 0xffffffff, expected 0xff00ff00 at (639, 479, 0), sub-resource 0. d3d11.c:28341: Test failed: Got 0xffffffff, expected 0xff00ff00 at (639, 479, 0), sub-resource 0.
=== debian11 (32 bit WoW report) ===
d3d11: d3d11.c:28278: Test failed: Got texcoord {8.43750119e-001, 1.56249881e-001}, expected {8.43750000e-001, 1.56250000e-001} at (3, 3), offset 1.25000000e-001. d3d11.c:28278: Test failed: Got texcoord {8.71093690e-001, 1.28906310e-001}, expected {8.71093750e-001, 1.28906250e-001} at (3, 3), offset 1.56250000e-002. d3d11.c:28278: Test failed: Got texcoord {7.51953065e-001, 2.48046935e-001}, expected {7.51953125e-001, 2.48046875e-001} at (3, 3), offset 4.92187500e-001. d3d11.c:28332: Test succeeded inside todo block: Got 0xffffffff, expected 0xffffffff at (640, 480, 1), sub-resource 0. d3d11.c:28341: Test succeeded inside todo block: Got 0xffffffff, expected 0xffffffff at (640, 480, 1), sub-resource 0. d3d11.c:28332: Test failed: Got 0xffffffff, expected 0xff00ff00 at (639, 479, 0), sub-resource 0. d3d11.c:28341: Test failed: Got 0xffffffff, expected 0xff00ff00 at (639, 479, 0), sub-resource 0. d3d11.c:28332: Test failed: Got 0xffffffff, expected 0xff00ff00 at (639, 479, 0), sub-resource 0. d3d11.c:28341: Test failed: Got 0xffffffff, expected 0xff00ff00 at (639, 479, 0), sub-resource 0.
On Thu, 3 Feb 2022 at 20:17, Zebediah Figura zfigura@codeweavers.com wrote:
- if (!use_mt)
- /* Running the tests multithreaded on 32-bit maps too much memory in Wine,
* even with only 2 threads. */
That didn't seem quite right, so I looked a bit more into this. It seems the issue is slightly more subtle; when maps start failing with GL_OUT_OF_MEMORY, the total number of chunks mapped across devices is typically either 0 or 1. On the other hand, the total number of allocated chunks tends to be fairly high (about 24, which would amount to about 1.5GiB). It seems the radeonsi driver doesn't actually (ever?) unmap buffers when we request that. That's probably reasonable enough for 64-bit applications, but less so for 32-bit applications. This doesn't happen on my Intel SKL system. A contributing factor is probably that because there's currently no slab allocator, we allocate blocks of WINED3D_ALLOCATOR_MIN_BLOCK_SIZE size for small constant buffers, which is going to inflate VRAM usage somewhat.
That leaves the question of what to do about it, of course. I could live with this series, although it seems a rather unsatisfying solution. We probably want to adjust the comment a little though, and I think we only want to do this on Wine, not on Windows (where running the tests in parallel always helped a bit more than on Wine anyway).
On 2/4/22 09:03, Henri Verbeet wrote:
On Thu, 3 Feb 2022 at 20:17, Zebediah Figura zfigura@codeweavers.com wrote:
- if (!use_mt)
- /* Running the tests multithreaded on 32-bit maps too much memory in Wine,
* even with only 2 threads. */That didn't seem quite right, so I looked a bit more into this. It seems the issue is slightly more subtle; when maps start failing with GL_OUT_OF_MEMORY, the total number of chunks mapped across devices is typically either 0 or 1. On the other hand, the total number of allocated chunks tends to be fairly high (about 24, which would amount to about 1.5GiB). It seems the radeonsi driver doesn't actually (ever?) unmap buffers when we request that. That's probably reasonable enough for 64-bit applications, but less so for 32-bit applications. This doesn't happen on my Intel SKL system. A contributing factor is probably that because there's currently no slab allocator, we allocate blocks of WINED3D_ALLOCATOR_MIN_BLOCK_SIZE size for small constant buffers, which is going to inflate VRAM usage somewhat.
Ugh, of course.
That leaves the question of what to do about it, of course. I could live with this series, although it seems a rather unsatisfying solution. We probably want to adjust the comment a little though, and I think we only want to do this on Wine, not on Windows (where running the tests in parallel always helped a bit more than on Wine anyway).
I guess I could also look into using multiple processes anyway. VRAM is still a theoretical concern, but maybe it won't really end up being important enough in practice.
It does feel like a nontrivial amount of work for something that's easy enough to solve with a sledgehammer, so I'm more than a little inclined just to disable multithreading on 32 bits, and then perhaps revisit this later.
This works fine currently, but won't once we start suballocating GL buffers.
Signed-off-by: Zebediah Figura zfigura@codeweavers.com --- dlls/dxgi/tests/dxgi.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/dlls/dxgi/tests/dxgi.c b/dlls/dxgi/tests/dxgi.c index a83964d7523..04f25e67740 100644 --- a/dlls/dxgi/tests/dxgi.c +++ b/dlls/dxgi/tests/dxgi.c @@ -93,7 +93,9 @@ static void run_queued_tests(void) SYSTEM_INFO si; LONG test_idx;
- if (!use_mt) + /* Running the tests multithreaded on 32-bit maps too much memory in Wine, + * even with only 2 threads. */ + if (!use_mt || sizeof(void *) == 4) { for (i = 0; i < mt_test_count; ++i) {
Hi,
While running your changed tests, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check?
Full results can be found at: https://testbot.winehq.org/JobDetails.pl?Key=106965
Your paranoid android.
=== debian11 (32 bit Arabic:Morocco report) ===
dxgi: dxgi.c:2669: Test failed: Got window rect (800,0)-(1600,600), expected (1024,0)-(1824,600). dxgi.c:2669: Test failed: Got monitor rect (800,0)-(1600,600), expected (1024,0)-(1824,600). dxgi.c:2683: Test failed: Got window rect (800,0)-(1600,600), expected (1024,0)-(1824,600). dxgi.c:2683: Test failed: Got monitor rect (800,0)-(1600,600), expected (1024,0)-(1824,600). dxgi.c:2686: Test failed: Got window rect (800,0)-(1600,600), expected (1024,0)-(1824,600). dxgi.c:2686: Test failed: Got monitor rect (800,0)-(1600,600), expected (1024,0)-(1824,600). dxgi.c:2700: Test failed: Got monitor rect (800,0)-(1824,737), expected (1024,0)-(2048,737). dxgi.c:2725: Test failed: Got monitor rect (800,0)-(1824,737), expected (1024,0)-(2048,737). dxgi.c:3356: Test failed: Got monitor rect (0,0)-(1360,768), expected (0,0)-(800,600). dxgi.c:3358: Test failed: Got monitor rect (0,0)-(1360,768), expected (0,0)-(800,600). dxgi.c:3371: Test failed: Got monitor rect (0,0)-(1360,768), expected (0,0)-(800,600).
=== debian11 (32 bit German report) ===
dxgi: dxgi.c:2616: Test failed: Got monitor rect (0,0)-(800,600), expected (0,0)-(1360,768). dxgi.c:2620: Test failed: Got monitor rect (0,0)-(800,600), expected (0,0)-(1360,768). dxgi.c:2689: Test failed: Got monitor rect (0,0)-(800,600), expected (0,0)-(1360,768). dxgi.c:2696: Test failed: Got monitor rect (0,0)-(800,600), expected (0,0)-(1360,768). dxgi.c:2689: Test failed: Got monitor rect (0,0)-(800,600), expected (0,0)-(1360,768). dxgi.c:2696: Test failed: Got monitor rect (0,0)-(800,600), expected (0,0)-(1360,768). dxgi.c:2711: Test failed: Got monitor rect (0,0)-(800,600), expected (0,0)-(1360,768). dxgi.c:2876: Test failed: Got monitor rect (0,0)-(800,600), expected (0,0)-(1360,768).
=== debian11 (32 bit Hebrew:Israel report) ===
dxgi: dxgi.c:3356: Test failed: Got monitor rect (0,0)-(1024,768), expected (0,0)-(800,600). dxgi.c:3358: Test failed: Got monitor rect (0,0)-(1024,768), expected (0,0)-(800,600). dxgi.c:3371: Test failed: Got monitor rect (0,0)-(1024,768), expected (0,0)-(800,600).
=== debian11 (32 bit Japanese:Japan report) ===
dxgi: dxgi.c:3672: Test failed: Got monitor rect (0,0)-(640,480), expected (0,0)-(800,600). dxgi.c:3701: Test failed: Got monitor rect (0,0)-(640,480), expected (0,0)-(800,600). dxgi.c:3646: Test failed: Got monitor rect (0,0)-(640,480), expected (0,0)-(800,600). dxgi.c:3672: Test failed: Got monitor rect (0,0)-(640,480), expected (0,0)-(800,600). dxgi.c:3701: Test failed: Got monitor rect (0,0)-(640,480), expected (0,0)-(800,600).
=== debian11 (32 bit Chinese:China report) ===
dxgi: dxgi.c:3356: Test failed: Got monitor rect (0,0)-(1360,768), expected (0,0)-(640,480). dxgi.c:3358: Test failed: Got monitor rect (0,0)-(1360,768), expected (0,0)-(640,480). dxgi.c:3371: Test failed: Got monitor rect (0,0)-(1360,768), expected (0,0)-(640,480).
=== debian11 (32 bit WoW report) ===
dxgi: dxgi.c:3646: Test failed: Got monitor rect (0,0)-(640,480), expected (0,0)-(1024,768). dxgi.c:3672: Test failed: Got monitor rect (0,0)-(640,480), expected (0,0)-(1024,768). dxgi.c:3701: Test failed: Got monitor rect (0,0)-(640,480), expected (0,0)-(1024,768). dxgi.c:3646: Test failed: Got monitor rect (0,0)-(640,480), expected (0,0)-(1024,768). dxgi.c:3672: Test failed: Got monitor rect (0,0)-(640,480), expected (0,0)-(1024,768). dxgi.c:3701: Test failed: Got monitor rect (0,0)-(640,480), expected (0,0)-(1024,768). dxgi.c:3646: Test failed: Got monitor rect (0,0)-(640,480), expected (0,0)-(1024,768). dxgi.c:3672: Test failed: Got monitor rect (0,0)-(640,480), expected (0,0)-(1024,768). dxgi.c:3701: Test failed: Got monitor rect (0,0)-(640,480), expected (0,0)-(1024,768). dxgi.c:7146: Test failed: Got a different mode.
=== debian11 (64 bit WoW report) ===
dxgi: dxgi.c:3356: Test failed: Got monitor rect (0,0)-(1360,768), expected (0,0)-(640,480). dxgi.c:3358: Test failed: Got monitor rect (0,0)-(1360,768), expected (0,0)-(640,480). dxgi.c:3371: Test failed: Got monitor rect (0,0)-(1360,768), expected (0,0)-(640,480).
-
Henri Verbeet -
Marvin -
Zebediah Figura