Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Message from discussion FF 3.5 and JS_GC Crashes

Path: g2news2.google.com!postnews.google.com!e27g2000yqm.googlegroups.com!not-for-mail
From: dbradley <dbrad...@gmail.com>
Newsgroups: mozilla.dev.apps.js-debugger,mozilla.dev.tech.javascript,mozilla.dev.platform,mozilla.dev.extensions
Subject: Re: FF 3.5 and JS_GC Crashes
Date: Sat, 25 Jul 2009 00:47:10 -0700 (PDT)
Organization: http://groups.google.com
Lines: 24
Message-ID: <a0f12dcd-7318-44b0-9f65-0ed70ce21c4c@e27g2000yqm.googlegroups.com>
References: <12fb6cfb-2fc7-4c1d-8403-5c56cee93603@o6g2000yqj.googlegroups.com> 
	<2513b20a-88c8-4e06-b2bc-1298d8dc272d@z34g2000vbl.googlegroups.com> 
	<ffd04002-e8b7-48c1-841a-75154c84257b@g23g2000vbr.googlegroups.com>
NNTP-Posting-Host: 174.101.221.240
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Trace: posting.google.com 1248508030 18291 127.0.0.1 (25 Jul 2009 07:47:10 GMT)
X-Complaints-To: groups-abuse@google.com
NNTP-Posting-Date: Sat, 25 Jul 2009 07:47:10 +0000 (UTC)
Complaints-To: groups-abuse@google.com
Injection-Info: e27g2000yqm.googlegroups.com; posting-host=174.101.221.240; 
	posting-account=liiQuQoAAAA7t-DGA0W5Y4MSpbIvvoZM
User-Agent: G2/1.0
X-HTTP-UserAgent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; 
	rv:1.9.0.13pre) Gecko/2009072405 GranParadiso/3.0.13pre (.NET CLR 
	3.5.30729),gzip(gfe),gzip(gfe)

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
> > > 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