[Bug 48815] New: user32:win "unexpected 0x738 message" Windows 10 failures

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=48815

Bug ID: 48815
           Summary: user32:win "unexpected 0x738 message" Windows 10
                    failures
           Product: Wine
           Version: unspecified
          Hardware: x86
                OS: Windows
            Status: NEW
          Severity: major
          Priority: P2
         Component: user32
          Assignee: [e-mail]
          Reporter: [e-mail]

user32:win sometimes fails complaining about an unexpected 0x738 message:

win.c:3858: Test failed: message 0738 available

or

win.c:3852: Test failed: hwnd 00210500 message 0738

This second message includes the window handle which means it is "always new",
which can cause the TestBot to mistakenly attribute the failure to the patch
being tested. So I bumped the priority on this bug.
> From what I gathered the 0x738 message was introduced in Windows 10 1703 which

is why this failure only happens on our 1709+ test configurations (we don't
have 1703). Also nobody seems to know what this message is, only that it seems
to be related to windows belonging to the UserAdapterWindowClass:

https://forums.zimbra.org/viewtopic.php?t=63188
https://stackoverflow.com/questions/44395364/windows-creators-update-crashes...
https://github.com/otya128/winevdm/issues/114

[Bug 48815] user32:win "unexpected 0x738 message" Windows 10 failures

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=48815

François Gouget  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |source, testcase

[Bug 48815] user32:win "unexpected 0x738 message" Windows 10 failures

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=48815

--- Comment #1 from François Gouget  ---
Created attachment 70312
  --> https://bugs.winehq.org/attachment.cgi?id=70312
user32:win Dump the 0x738 messages

The attached patch confirms that the 0x738 message is sent to a message-only
UserAdapterWindowClass window:

win.c:4049: Test failed: message 0738 available
win.c:55: hwnd=00000000000301C0 pid=5144 tid=6984 now=68609
win.c:56: hwnd=00000000000201BA message=0738 wParam=0 lParam=0 time=68593
pt=(250,250)
win.c:60: wnd: parent=0000000000000000 owner=0000000000000000
win.c:65: wnd: pid=5144 tid=6984 class=22 L"UserAdapterWindowClass" text=0 L""
win.c:72: hwnd=00000000000201BA is a message-only window

[Bug 48815] user32:win "unexpected 0x738 message" Windows 10 failures

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=48815

Rémi Bernon  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED
      Fixed by SHA1|                            |fa28e05cf5b0101fb046c484539
                   |                            |1634791268200
                 CC|                            |[e-mail]

--- Comment #2 from Rémi Bernon  ---
This should be fixed with fa28e05cf5b0101fb046c4845391634791268200. Messages
for windows of the UserAdapterWindowClass classs are now ignored.

[Bug 48815] user32:win "unexpected 0x738 message" Windows 10 failures

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=48815

Alexandre Julliard  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |CLOSED

--- Comment #3 from Alexandre Julliard  ---
Closing bugs fixed in 7.2.