On 10/2/2014 1:08 AM, Mark Weaver wrote: > On 27/09/2014 20:59, Sean Hall wrote: >> Can someone that can reproduce this try calling PostQuitMessage on the >> WM_NCDESTROY message instead of WM_DESTROY? >> >> SHAutoComplete documentation says you need to wait for the control to be >> destroyed before calling CoUninitialize. Since the window gets the >> WM_DESTROY message before its child controls, the control is probably >> never being destroyed. If we wait for the WM_NCDESTROY message instead, >> the control will be destroyed when we call PostQuitMessage. >> > Yes, delaying the call to PostQuitMessage until WM_NCDESTROY appears to > cure the issue. (I have checked this carefully ensuring the only > difference between the two wixstdba dlls is the position of that line > and that one hangs when run via winrs and one does not).
Awesome - such a simple fix after the bug has been open such a long time! I see 3.9 is still at RC3 - any chance this could make it into 3.9 RTM? -- Bruce ------------------------------------------------------------------------------ Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk _______________________________________________ WiX-devs mailing list WiX-devs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-devs
