On 11/3/09 1:40 PM, Georgios Petasis wrote:
Yes, using instructions from https://developer.mozilla.org/en/Debugging_memory_leaks. But I reach no conclusions...
Well, what was the refcount imbalance on your documents, say?
I tried to do the following: /* Create our session history object and tell the navigation object * to use it. We need to do this before we create the web browser * window... */ mSessionHistory = do_CreateInstance(NS_SHISTORY_CONTRACTID, &rv); mNavigation->SetSessionHistory(mSessionHistory); if (NS_FAILED(rv)) return rv;
I believe this should make session history work....
In the way I call XRE_InitEmbedding, mXulDir = mAppDir, and is the parent directory xpcom.so was found. Should I use something else?
I don't know the right way to set up a profile, sorry. Maybe someone else will.
I have the feeling that despite the fact that my AddRef() & Release() are balanced, each page I load remains alive "somewhere". I don't know where though :-)
Right. That's where those refcount balance trees can sometimes help. And yes, reading them takes some effort...
In fact this happens when I call exit, from a thread different than the thread mozilla runs. It seems that mozilla registers some callbacks that trigger on exit, and these are triggered from a different thread?
The module destructors, for example?
Isn't this the correct usage of GetProxy?
Sounds like it, yes. -Boris _______________________________________________ dev-embedding mailing list [email protected] https://lists.mozilla.org/listinfo/dev-embedding
