December 2022 - Wine-Bugs - list.winehq.org

[Bug 54152] New: mshtml:misc sometimes times out in Wine
by WineHQ Bugzilla Dec. 15, 2022

Dec. 15, 2022

https://bugs.winehq.org/show_bug.cgi?id=54152 Bug ID: 54152 Summary: mshtml:misc sometimes times out in Wine Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: mshtml Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- mshtml:misc sometimes times out on exit in Wine. Sometimes the timeout happens on exit: 0a50:misc: 244 tests executed (0 marked as todo, 0 as flaky, 0 failures), 0 skipped. mshtml:misc:0a50 done (258) in 120s 86B and sometimes before in which case there is no trace: mshtml:misc:04c0 done (258) in 120s 0B See https://test.winehq.org/data/patterns.html#mshtml:misc The first timeout happened on 2022-11-10 but there is only a bit over 1 per month. Also the GitLab CI seems to be more prone to getting those. There is also one case where the test got a failure instead: misc.c:257: Test failed: key failed 80004005 0a4c:misc: 244 tests executed (0 marked as todo, 0 as flaky, 1 failure), 0 skipped. mshtml:misc:0a4c done (1) in 0s 131B 256 hres = IHTMLStorage_key(storage, -1, &key); 257 ok(hres == E_INVALIDARG, "key failed %08lx\n", hres); Where: 0x80004005 == E_FAIL 0x80070057 == E_INVALIDARG Hopefully that failure is related and the timeout is caused by either HTMLStorage_key() going into an infinite loop or corrupting the memory. -- 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.

1 2

[Bug 54047] New: wiaservc:wia sometimes crashes on Windows 11
by WineHQ Bugzilla Dec. 15, 2022

Dec. 15, 2022

https://bugs.winehq.org/show_bug.cgi?id=54047 Bug ID: 54047 Summary: wiaservc:wia sometimes crashes on Windows 11 Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: wia Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com wiaservc:wia sometimes crashes on Windows 11: 0d78:wia: unhandled exception c0000005 at 00007FFE62E43777 See https://test.winehq.org/data/patterns.html#wiaservc:wia This failure is pretty rare and since there is no trace or backtrace whatsoever it's unclear where the crash occurs. Note: On Windows 10 21H1+ it times out instead of crashing (see bug 54046). These two issues may well be related (memory corruption?). -- 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.

1 3

[Bug 54154] New: winmm:midi sometimes crashes on exit in Wine
by WineHQ Bugzilla Dec. 15, 2022

Dec. 15, 2022

https://bugs.winehq.org/show_bug.cgi?id=54154 Bug ID: 54154 Summary: winmm:midi sometimes crashes on exit in Wine Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: winmm&mci Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- winmm:midi sometimes crashes on exit in Wine: 0494:midi: 445 tests executed (4 marked as todo, 0 as flaky, 0 failures), 0 skipped. winmm:midi:0494 done (-1073741819) in 7s 5788B See https://test.winehq.org/data/patterns.html#winmm:midi Where -1073741819 == 0xc0000005 The pid of the test summary line matches the one printed by the WineTest executable which means this is the summary line of the main process. That means the crash happens on exit, probably as the result of memory / stack corruption. There have been 24 crashes in the past 6 months but they became more frequent after the 2022-09-16 which may correspond to the TestBot switching to running two VMs are a time. So the failure may be caused by extra load. There is also at least one case of a timeout on exit (2022-12-09 on debian11-win32-ja-JP), which is probably the same issue: 05fc:midi: 445 tests executed (4 marked as todo, 0 as flaky, 0 failures), 0 skipped. winmm:midi:05fc done (258) in 120s 5788B -- 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.

1 1

[Bug 54153] New: kernel32:debugger - test_kill_on_exit() sometimes gets STILL_ACTIVE exit code on Windows
by WineHQ Bugzilla Dec. 15, 2022

Dec. 15, 2022

https://bugs.winehq.org/show_bug.cgi?id=54153 Bug ID: 54153 Summary: kernel32:debugger - test_kill_on_exit() sometimes gets STILL_ACTIVE exit code on Windows Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com kernel32:debugger - test_kill_on_exit() sometimes gets STILL_ACTIVE exit code on Windows: debugger.c:2078: Test failed: exit code = 00000103 See https://test.winehq.org/data/patterns.html#kernel32:debugger Where 0x103 == STILL_ACTIVE == STATUS_PENDING This should mean the process is still running. So either there is a race condition in the test or Windows 8 and 10 21H1 are buggy. With only 3 instances in 6 months this failure is pretty rare: * 2022-07-11 on w10pro64-ar (64-bit, 21H1) * 2022-10-31 on w864 (64-bit) * 2022-12-06 on w864 (64-bit) -- 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.

1 1

[Bug 54128] New: user32:msg - test_PeekMessage3() sometimes gets an unexpected WM_TIMECHANGE message on Windows 10
by WineHQ Bugzilla Dec. 15, 2022

Dec. 15, 2022

https://bugs.winehq.org/show_bug.cgi?id=54128 Bug ID: 54128 Summary: user32:msg - test_PeekMessage3() sometimes gets an unexpected WM_TIMECHANGE message on Windows 10 Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: user32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com test_PeekMessage3() sometimes gets an unexpected WM_TIMECHANGE message on Windows 10: msg.c:13549: Test failed: msg.message = 30 instead of WM_TIMER msg.c:13552: Test failed: msg.message = 275 instead of WM_USER + 1 msg.c:13554: Test failed: expected PeekMessage to return FALSE, got 1 msg.c:13564: Test failed: msg.message = 1025 instead of WM_TIMER msg.c:13566: Test failed: msg.message = 275 instead of WM_USER msg.c:13568: Test failed: expected PeekMessage to return FALSE, got 1 msg.c:13577: Test failed: msg.message = 1024 instead of WM_TIMER msg.c:13579: Test failed: expected PeekMessage to return FALSE, got 1 See https://test.winehq.org/data/patterns.html#user32:msg Where 30 == WM_TIMECHANGE 275 == WM_TIMER 1024 == WM_USER 1025 == WM_USER + 1 This is similar to the issue happening in test_PeekMessage2() in bug 53273. This last happened on 2022-12-09 on w10pro64-pt-BR where the Internet time synchronization has not been disabled. So that may be the source of the WM_TIMECHANGE messages. The TestBot now has code to disable Internet time synchronization but the snapshots have not all been updated. So this bug should be revisited once they have been updated to see if the failures are still happening. -- 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.

1 1

[Bug 54076] New: windows.globalization:globalization - test_GlobalizationPreferences() sometimes unexpectedly returns en_US on Windows 10
by WineHQ Bugzilla Dec. 15, 2022

Dec. 15, 2022

https://bugs.winehq.org/show_bug.cgi?id=54076 Bug ID: 54076 Summary: windows.globalization:globalization - test_GlobalizationPreferences() sometimes unexpectedly returns en_US on Windows 10 Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com windows.globalization:globalization - test_GlobalizationPreferences() sometimes unexpectedly returns en_US on Windows 10: globalization.c:137: Test failed: IGlobalizationPreferencesStatics_get_Languages 0 returned len 5, str L"en-US", expected L"de-DE" globalization.c:177: Test failed: IGlobalizationPreferencesStatics_get_Languages 0 returned len 5, str L"en-US", expected L"de-DE" See https://test.winehq.org/data/patterns.html#ws2_32:sock This failure first happened on 2022-11-22 and impacts the de, fr, ja, ko, pt-BR and ru locales of the w10pro64 VM. It's not systematic but is frequent enough that it seems like it does not impact the other locales. The timing of the first failure is suspicious: * The w10pro64 had a problem where Windows 10 would reset UserDefaultLCID, ThreadLocale and Country to en_US when the TestBot called SetSystemTime() to update the clock in the live snapshot. As long as this issue was there there was no failure. * On 2022-11-21 LibvirtTool got a workaround to re-set these locale settings after setting the time and the failures started. So this sounds like Windows is still messing with the locales :-( -- 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.

1 3

[Bug 54147] New: Kholat from GOG: Splash video are not in fullscreen
by WineHQ Bugzilla Dec. 14, 2022

Dec. 14, 2022

https://bugs.winehq.org/show_bug.cgi?id=54147 Bug ID: 54147 Summary: Kholat from GOG: Splash video are not in fullscreen Product: Wine Version: 8.0-rc1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: mfplat Assignee: wine-bugs(a)winehq.org Reporter: titan.costa(a)gmail.com Distribution: --- Wine wine-8.0-rc1. Ubuntu 22.10. >From bug https://bugs.winehq.org/show_bug.cgi?id=50043. -- 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.

1 1

[Bug 52930] New: d3dcompiler_47:hlsl_d3d9 fails randomly on Windows
by WineHQ Bugzilla Dec. 14, 2022

Dec. 14, 2022

https://bugs.winehq.org/show_bug.cgi?id=52930 Bug ID: 52930 Summary: d3dcompiler_47:hlsl_d3d9 fails randomly on Windows Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: directx-d3d-util Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Created attachment 72305 --> https://bugs.winehq.org/attachment.cgi?id=72305 Small patch to apply on top of 58d20aae3772^ to get failures d3dcompiler_47:hlsl_d3d9 fails randomly on Windows 8.1 to 21H2: hlsl_d3d9.c:1691: Test failed: Got unexpected hr 0x88760b59. hlsl_d3d9.c:1692: Test failed: Got unexpected blob. hlsl_d3d9.c:1693: Test failed: Got unexpected errors. https://test.winehq.org/data/patterns.html#d3dcompiler_47:hlsl_d3d9 A bisect against Windows 10 21H1 on cw-gtx560 shows that the failures started with the commit below: commit 58d20aae3772473a90e43ee236b793f0421eecb1 Author: Eric Pouech <eric.pouech(a)gmail.com> Date: Tue Feb 8 19:48:44 2022 +0100 d3dcompiler/tests: Build without -DWINE_NO_LONG_TYPES. Signed-off-by: Eric Pouech <eric.pouech(a)gmail.com> Signed-off-by: Henri Verbeet <hverbeet(a)codeweavers.com> Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> The patch does not actually make any change that should matter but I have confirmed the bisect result manually: 58d20aae3772^ -> 200 consecutive runs with no failure 58d20aae3772 -> fails after 9 to 33 runs - Applying just the Makefile.in parts and last 4 chunks of hlsl_d3d9.c of that commit is sufficient to get the failures. - Patching only the makefiles is not enough. - I did not try to identify which of the 4 chunks are needed to get failures. They all patch code that's executed after the failure anyway. So there must be some memory corruption that's sensitive to memory layout or some subtle issue with the generated code. I also if(0)ed-out all the other test_xxx() functions, and also if(0)ed-out the tests that preceded the failing one in test_include() but I still get the failure so it's not a case where an ill-advised NULL-behavior test causes memory corruption. -- 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.

1 5

[Bug 54138] New: wine/debug.h does not compile in Visual Studio with native headers due to undefined __has_attribute
by WineHQ Bugzilla Dec. 13, 2022

Dec. 13, 2022

https://bugs.winehq.org/show_bug.cgi?id=54138 Bug ID: 54138 Summary: wine/debug.h does not compile in Visual Studio with native headers due to undefined __has_attribute Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: dimaki(a)rocketmail.com Distribution: --- wine/debug.h does not compile in Visual Studio with native headers due to undefined __has_attribute. Other headers in Wine that use __has_attribute have below code. Probably this or something similar needed in debug.h as well. #ifndef __has_attribute #define __has_attribute(x) 0 #endif -- 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.

1 2

[Bug 54133] New: A WM_CLIPCHILDREN window's repaint region is not computed correctly when its child is resized or repositioned
by WineHQ Bugzilla Dec. 13, 2022

Dec. 13, 2022

https://bugs.winehq.org/show_bug.cgi?id=54133 Bug ID: 54133 Summary: A WM_CLIPCHILDREN window's repaint region is not computed correctly when its child is resized or repositioned Product: Wine Version: 7.12 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: wineserver Assignee: wine-bugs(a)winehq.org Reporter: jinoh.kang.kr(a)gmail.com Regression SHA1: 33617af8145b6fadfe41d48968a728ff57b3064b Distribution: --- Wine sometimes under-calculates the repaint region of WM_CLIPCHILDREN windows with a child window that has been resized or repositioned. The regression started with the following commit: commit 33617af8145b6fadfe41d48968a728ff57b3064b Author: Jinoh Kang <jinoh.kang.kr(a)gmail.com> Date: Mon Oct 31 22:30:20 2022 +0900 server: Don't invalidate the newly exposed child region on the parent if it doesn't clip children. This partly reverts e42eaaaf3a873d29b14f8f3a3617df2d0d4210ca. Signed-off-by: Jinoh Kang <jinoh.kang.kr(a)gmail.com> -- 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.

1 4