[EMAIL PROTECTED] (James Warner) writes: > Dan, > > Thanks for the heads up on the bugs.... but since this seems to work > up to this point I think I'll just forgo the debug builds (probably > a big mistake but oh well).
This will open up one or more race conditions, which could ultimately end up in leaking an object or attempting to doubly-free it. I'm not sure how likely this is; perhaps not much. > However, I'm having a little bit of trouble cleaning up after the > Windows close. > At present I Have the proxy object do the OpenWindow and perform the > interaction inside the window, which basically consists of a bunch of > JS things, etc. After the close button is pushed I have an observer > set up to listen for the "domwindowclosed" event. After trapping this > event I call nsPIWindowWatcher->RemoveWindow on the Window that was > passed to the Observer. However, after doing that I'm still left with > about 800KB of space that doesn't get freed. So the question is.... > What needs to be freed after a DOMWindow is closed to regain the > resources that it acquired? This is outside my area of expertise; someone else will need to pipe up to answer this (maybe the .embedding newsgroup would be a good place to ask). Dan
