https://bugs.winehq.org/show_bug.cgi?id=36597
--- Comment #6 from Austin English austinenglish@gmail.com --- (In reply to Sebastian Lackner from comment #5)
Regarding the new valgrind complains you pointed out on IRC ( http://pastebin.com/UQ7Qjagi ): They don't seem to be related at my opinion, except there is also an additional test failure. Is there any?
BTW: Do you already have any clue why we have all the test failures in user32/tests/msg.c when running with Valgrind (I assume they aren't there without Valgrind on your machine)? It looks like they start even before the first Valgrind warning, which is a bit weird?!
Yeah, some test failures: msg.c:9145: Test failed: ScrollWindowEx: 10: the msg sequence is not complete: expected 0000 - actual 001f msg.c:6976: Test failed: MsgWaitForMultipleObjects failed 102 msg.c:13540: Test failed: key press only: 0: the msg sequence is not complete: expected 0100 - actual 0000 msg.c:13546: Test failed: unexpected key state 0 msg.c:13552: Test failed: key press repeat: 0: the msg sequence is not complete: expected 0100 - actual 0000 msg.c:13558: Test failed: unexpected key state 0 msg.c:13564: Test failed: key release repeat: 0: the msg sequence is not complete: expected 0101 - actual 0000
(those may be timing related, though).