http://bugs.winehq.org/show_bug.cgi?id=20692
--- Comment #3 from Nikolay Sivov bunglehead@gmail.com 2009-11-13 23:13:31 --- (In reply to comment #1)
Not likely to hurt any real app.
It affects any app that uses ListView for example - any window that blocks WM_NCDESTROY flow to default procedure. It's a real problem and a leak with obvious reason. Dan, please consider to reopen this.
A fix is two-line: --- HeapFree( GetProcessHeap(), 0, wndPtr->text ); wndPtr->text = NULL; ---
Should be placed in WIN_DestroyWindow(). I've already done that for scrollinfo.
I'll prepare patches both for ListView and destroy sequence (I want ListView to call default procedure after its own releasing).