Message from discussion FF 3.5 and JS_GC Crashes
From: dbradley <dbrad...@gmail.com>
Subject: Re: FF 3.5 and JS_GC Crashes
Date: Sat, 25 Jul 2009 00:47:10 -0700 (PDT)
Content-Type: text/plain; charset=ISO-8859-1
X-Trace: posting.google.com 1248508030 18291 127.0.0.1 (25 Jul 2009 07:47:10 GMT)
NNTP-Posting-Date: Sat, 25 Jul 2009 07:47:10 +0000 (UTC)
Injection-Info: e27g2000yqm.googlegroups.com; posting-host=188.8.131.52;
X-HTTP-UserAgent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US;
rv:184.108.40.206pre) Gecko/2009072405 GranParadiso/3.0.13pre (.NET CLR
On Jul 24, 11:45=A0am, Glenn Boysko <gboy...@gmail.com> 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
> > 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.