[Bug 54975] New: win32u:win32u exits prematurely, leaves child process behind, interferes with windows.globalization:globalization
https://bugs.winehq.org/show_bug.cgi?id=54975 Bug ID: 54975 Summary: win32u:win32u exits prematurely, leaves child process behind, interferes with windows.globalization:globalization Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: win32u Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- win32u:win32u exits prematurely, leaves child process behind: win32u:win32u start dlls/win32u/tests/win32u.c [...] win32u.c:1037: Test marked todo: res = 4 win32u.c:1040: Test marked todo: buf[1] = 0 win32u:win32u:09f0 done (0) in 0s 1295B win32u.c:1045: Test failed: res = 0 win32u.c:1046: Test failed: buf = d win32u.c:1049: Test failed: res = 0 win32u.c:1059: Test failed: res = 0 09e0:win32u: 14 tests executed (2 marked as todo, 0 as flaky, 4 failures), 0 skipped. See https://test.winehq.org/data/patterns.html#win32u:win32u There are two things to notice in the above log: * The main win32u:win32u process is 09e0 but it did not issue a 'tests executed' summary. This means it exited prematurely. * 09e0 is a child process that continues running and printing messages which interferes with the next test, specifically windows.globalization:globalization. Also on the TestBot one can find the corresponding Wine log which contains these lines that seem strongly correlated to this issue: 0480:err:seh:KiUserCallbackDispatcher ignoring exception 0480:err:seh:KiUserCallbackDispatcher ignoring exception wine client error:480: partial write 57344 Running: win32u:win32u (694 of 774) Running tests - 6 failures This issue only happens on Linux and happens systematically but only on three configurations: fg-deb64-t32 but not for the wow32 and wow64 builds on the same machine fgtb-debian11-wow64 but not for the wow32 build on the same machine debian11b-wow64 but but not for the wow32 build on the same machine (and none of the 32-bit builds on debian11 is impacted) And I have been unable to reproduce this failure on my machine (fg-deb64-t32). So it's unclear what causes this failure but it clearly started on 2023-05-15 so it's probably some commit on that day. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=54975 François Gouget <fgouget(a)codeweavers.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |source, testcase -- 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.
https://bugs.winehq.org/show_bug.cgi?id=54975 zmtong1988(a)gmail.com <zmtong1988(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |zmtong1988(a)gmail.com --- Comment #1 from zmtong1988(a)gmail.com <zmtong1988(a)gmail.com> --- debian11 it does exist. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=54975 --- Comment #2 from zmtong1988(a)gmail.com <zmtong1988(a)gmail.com> --- (In reply to zmtong1988(a)gmail.com from comment #1)
debian11 it does exist.
00e0:00e4:err:seh:KiUserCallbackDispatcher ignoring exception 00e0:00e4:err:seh:KiUserCallbackDispatcher ignoring exception 00e0:00e4:err:seh:KiUserCallbackDispatcher ignoring exception 00e0:00e4:err:seh:KiUserCallbackDispatcher ignoring exception 00e0:00e4:err:seh:KiUserCallbackDispatcher ignoring exception -- 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.
https://bugs.winehq.org/show_bug.cgi?id=54975 Bernhard Übelacker <bernhardu(a)mailbox.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bernhardu(a)mailbox.org --- Comment #3 from Bernhard Übelacker <bernhardu(a)mailbox.org> --- Hello, is it possible to check if this patch helps on the affected systems? https://www.winehq.org/pipermail/wine-devel/2021-December/203292.html -- 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.
https://bugs.winehq.org/show_bug.cgi?id=54975 --- Comment #4 from François Gouget <fgouget(a)codeweavers.com> --- Unfortunately I have been unable to reproduce the failure despite it happening systematically in the nightlies (it's quite frustrating) so I would be unable to confirm that it is gone. But if this patch gets applied we should be able to quickly see if it helps at least. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=54975 --- Comment #5 from Bernhard Übelacker <bernhardu(a)mailbox.org> --- That is unfortunate. I just wanted to mention this here because of the "wine client error:480: partial write 57344", which i do regularly see when I try to record a wine process tree with rr-debugger. I guess that is also the reason why Keno Fischer developed this patch. Unfortunately I don't see any more current submission attempts of this patch by him for this patch. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=54975 --- Comment #6 from François Gouget <fgouget(a)codeweavers.com> --- It looks like this stopped failing on 2023-06-05 despite there being no commit to win32u:win32u on that date. -- 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.
http://bugs.winehq.org/show_bug.cgi?id=54975 --- Comment #7 from Bernhard Übelacker <bernhardu(a)mailbox.org> --- The patch I was proposing in comment #3 about the "partial write" got committed in modified form here: https://gitlab.winehq.org/wine/wine/-/commit/cd197f8588 (But that partial write was maybe just a symptom of an earlier issue.) -- 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.
participants (1)
-
WineHQ Bugzilla