Boris Zbarsky wrote:
Niky Williams wrote:
A basic navigate to google.com and then shutdown of my app yeilds
about the same "leakage" as the MFCEmbed app does. Here is where I'm
a little confused...if I click on the link to froogle and then shut
down, I get a WHOLE lot of reported leaks.
Sounds to me like the froogle site triggers a leak.
Something else I noticed. I WAS getting that nsWindow, nsWebBrowser
and one other...dang can't remember..were leaking...I changed my
nsIWebBrowser object from an nsCOMPtr to a standard raw pointer and
released them myself on shutdown and it got rid of those leaks. I'm
wondering...since it was an nsCOMPtr, could it be that the leak stats
finished up before the nsCOMPtr had a chance to call the destructor on
that object?
It's possible; when is your nsCOMPtr getting destroyed?
-Boris
Boris,
Thanks for the reply!
I'm assuming it [nsCOMPtr] gets destroyed at the end of my program after
I release my chrome. I have not traced that deep yet. The
nsIWebBrowser is the browser object for my chrome and so I was letting
the nsCOMPtr take care of the destruction of that object. I don't mind
using a raw pointer, was just curious for any explanation.
Niky Williams
_______________________________________________
dev-embedding mailing list
dev-embedding@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-embedding
