https://bugs.winehq.org/show_bug.cgi?id=18985
--- Comment #29 from Damjan Jovanovic damjan.jov@gmail.com --- Why does that message crash the application? It's one or more of the following: 1. The message contents are wrong. 2. The message is sent when it shouldn't be. 3. The message is sent synchronously using SendMessage() instead of asynchronously using PostMessage(). 4. The message and its timing are right, but the listview state is wrong in some other way, and that message just triggers the processing that crashes as a result of that wrongness.
(Hopefully it's one of the easier cases, as dlls/comctl32/listview.c is 11948 lines long...)
1. A WINEDEBUG='+listview' log shows: 002c:trace:listview:notify_listview (code=-101, plvnm=iItem=0, iSubItem=0, uNewState=0x0, uOldState=0x0, uChanged=0x1, ptAction=(0,0), lParam=26371760) which is also sent earlier and doesn't crash. 2. Nope. It gets sent the same way several times, only the 4th time crashes. 3. Not possible, our tests use SendMessage() too. 4. Sadly, this is probably it.