http://bugs.winehq.org/show_bug.cgi?id=6801
--- Comment #45 from Hin-Tak Leung htl10@users.sourceforge.net 2008-04-17 14:49:41 --- (In reply to comment #44) <snipped>
I think that crash which I'm talking about is because of wrong memory release order in ReleaseWebBrowser (dlls/hhctrl.ocx/webbrowser.c). It should be:
- info->web_browser
- info->wb_object
- info->client_site
But first I need to know if crash (and solution) occurs not only in my environment?
So... do you confirm that crash?
<snipped>
I don't think I understand that part of the code, although I have tried in the past. I think the window handle patch (or a corrected patch for it, if I made a mistake) is a must, because the parent must keep track of daughter windows and releases resources correctly - the unpatched git code is just wrong (and as it says, it has two FIXME's); secondly, the resources management must deal with multiple help windows correctly (or just let it leak, rather than crash; and wait for a proper fix for the leak later).
I haven't had a crash lately, since the local windows handle patch, but maybe I am just not trying hard enough :-).