Re: FF 3.5 and JS_GC Crashes
Glenn Boysko <[email protected]> Mon, 27 Jul 2009 07:55:00 -0700 (PDT)
| Newsgroups | gmane.comp.mozilla.devel.jsdebugger |
|---|---|
| Organization | http://groups.google.com |
| Message-ID | <8649765f-62cf-4184-90e8-4241ef856406@v36g2000yqv.googlegroups.com> |
David: > Sounds like your fine. The timer fires on the main thread event queue. > I just wanted to make sure you were specifically creating a thread to > do some work and invoking some JS code on that. That causes lots of > problems, since GC is to only occur on the main thread. 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). 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). 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? Thanks, Glenn