Re: FF 3.5 and JS_GC Crashes

On Jul 27, 10:55 am, Glenn Boysko <[email protected]> wrote:
> David:
>
> Thanks for the reply. What about the callbacks from
> jsdIDebuggerService methods (e.g., enumerateScripts)? Are they called
> back on the main thread? Same goes for the nsIWebProgressListener
> callbacks (e.g., onStateChange).

Pretty sure they don't. Most of the Mozilla code is event driven and
only a few things like Necko use threads and then it's very isolated.

> Can you get GC problems if you don't call QueryInterface in JS code?
> I'm thinking specifically of the instances supplied in
> nsIWebProgressListener callbacks (e.g., going from nsIRequest to
> nsIHttpChannel).

That wouldn't cause GC problems. If something was off there, XPConnect
would detect it and return an error.

> Any suggestions are appreciated. Can a debug version of FF help to
> identify the source of these crashes? Can I get debug versions of FF
> without building them on my own machine?

Yes, there is diagnostics and logging that you can turn on in a debug
build.  However I don't know of any distributions of debug builds. So
I think the only solution is to build it yourself.