Re: FF 3.5 and JS_GC Crashes

dbradley <[email protected]> Sat, 25 Jul 2009 00:47:10 -0700 (PDT)
Newsgroups gmane.comp.mozilla.devel.jsdebugger
Organization http://groups.google.com
Message-ID <a0f12dcd-7318-44b0-9f65-0ed70ce21c4c@e27g2000yqm.googlegroups.com>
On Jul 24, 11:45 am, Glenn Boysko <[email protected]> wrote:
> > > We are finding many crashes associated with Firefox 3.5 that we are
> > > not seeing with FF 3.0.x. The debug stacks seem to indicate failures
> > > in JS_GC and other JavaScript related APIs.
>
> > Are any of the calls to the JS component on a thread other than the
> > main thread?
>
> I believe that all of the calls to the JS XPCOM component are on the
> main thread. The JS XPCOM component creates a Timer and updates a
> series of broadcast elements when the timer is handled. Does that mean
> that the JS XPCOM component is being called (internally) on another
> thread if it invoked from a nsITimer?
>
> If it was being invoked from another thread (other than the main),
> what should we do? Are there specially precautions I can take to
> prevent GC crashes?

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.

David