"Benjamin Smedberg" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > Phil McLachlan wrote: > >> Leaking on shutdown may not be much of a problem, in an application that >> saves shutdown for just prior to terminating the process/application. >> However, the web control can be instantiated and destroyed repeatedly >> while browsing several different web pages. > > The Mozilla control may be instantiated multiple times, but XPCOM > currently can only be instantiated once per process. If you try to > shutdown and reinitialize XPCOM all kinds of bad things can happen (and I > think we actually prevent that with a static guard). So this isn't really > a big issue. > > --BDS
Thanks for the fast response. FYI, multiple shutdown and initializations per process does work sometimes. What can be done to coax XPConnect to release it's references to objects, so there is no memory hanging around in Mozilla and IE long after the control has been destroyed? I've tried JS_ClearScope and JS_GC, but that doesn't always seem to release everything. _______________________________________________ dev-tech-xpcom mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-xpcom
