https://bugs.winehq.org/show_bug.cgi?id=51399
Bug ID: 51399 Summary: Together ntoskrnl.exe:ntoskrnl and user32:monitor trigger extra user32:win failures Product: Wine Version: 6.10 Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: user32 Assignee: wine-bugs@winehq.org Reporter: fgouget@codeweavers.com
When ntoskrnl.exe:ntoskrnl is run before user32:win it triggers 4 failures in the latter (see bug 51391). And when user32:monitor is run before user32:win it triggers 3 failures (see bug 51392).
But when both ntoskrnl.exe:ntoskrnl and user32:monitor are run before user32:win they trigger an extra set of 15 failures:
win.c:5162: Test failed: wrong update region win.c:5177: Test failed: wrong update region win.c:5195: Test failed: wrong update region win.c:5197: Test failed: unexpected update rect: (20,40)-(29,50) win.c:5211: Test failed: wrong update region win.c:5221: Test failed: wrong update region in excessive scroll win.c:5243: Test failed: wrong update region win.c:5252: Test failed: wrong update region win.c:5261: Test failed: wrong update region win.c:5276: Test failed: wrong update region win.c:5352: Test failed: pixel should be black, color is ffffffff win.c:5356: Test failed: pixel should be black, color is ffffffff win.c:5361: Test failed: rects do not match (0,0)-(30,100) / (0,0)-(100,100) win.c:5372: Test failed: wrong update region win.c:5383: Test failed: wrong update region
Furthermore: * Order is important: ntoskrnl.exe:ntoskrnl user32:monitor user32:win has the extra failures, but not user32:monitor ntoskrnl.exe:ntoskrnl user32:win! * And this is specific to Vista and Windows 7; probably because these failures don't happen if there is no left-over ntoskrnl.exe dialog (including if it is closed manually after running the test). * This second point probably means that the left-over dialog changes the user32:monitor behavior. But if so there is no indication of this in the user32:monitor traces (and obviously no failure there).