From owner-freebsd-gecko@FreeBSD.ORG  Tue May 20 10:04:30 2014
Return-Path: <owner-freebsd-gecko@FreeBSD.ORG>
Delivered-To: gecko@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 2968D2AD;
 Tue, 20 May 2014 10:04:30 +0000 (UTC)
Received: from outgoing.tristatelogic.com (segfault.tristatelogic.com
 [69.62.255.118])
 by mx1.freebsd.org (Postfix) with ESMTP id 0EB37236F;
 Tue, 20 May 2014 10:04:29 +0000 (UTC)
Received: from segfault-nmh-helo.tristatelogic.com (localhost [127.0.0.1])
 by segfault.tristatelogic.com (Postfix) with ESMTP id A38403AF0D;
 Tue, 20 May 2014 03:04:20 -0700 (PDT)
From: "Ronald F. Guilmette" <rfg@tristatelogic.com>
To: Kevin Oberman <rkoberman@gmail.com>, gecko@FreeBSD.org,
 freebsd-ports@freebsd.org
Subject: Re: firefox-29.0,1 -- dumps core
In-Reply-To: <CAN6yY1sk8swT1WHXjj7HXredHmQm0d4Pi=-gsvMJpbNsq+TueQ@mail.gmail.com>
Date: Tue, 20 May 2014 03:04:20 -0700
Message-ID: <79472.1400580260@server1.tristatelogic.com>
X-BeenThere: freebsd-gecko@freebsd.org
X-Mailman-Version: 2.1.18
Precedence: list
List-Id: Gecko Rendering Engine issues <freebsd-gecko.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-gecko>,
 <mailto:freebsd-gecko-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-gecko/>
List-Post: <mailto:freebsd-gecko@freebsd.org>
List-Help: <mailto:freebsd-gecko-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-gecko>,
 <mailto:freebsd-gecko-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 20 May 2014 10:04:30 -0000



Please allow me to clarify two things:

1)  The exact set of build options that are needed in order to reproduce
    the crash I have reported are as follows:

	DBUS (enabled by default)
	GIO (enabled by default)
	GSTREAMER (enabled by default)
	ALSA (enabled by default)

	DEBUG

Apparently enabling or disabling the LOGGING option makes no difference
at all.  The crash will arise (when broswing around on, e.g. www.newegg.com)
as long as the DEBUG build-time option is enabled.

2)  When built with DEBUG, Firefox is quite a bit more verbose than when
it is built without that option.  In particular, some text messages that
Firefox writes to its stderr channel just before it segfaults appear to
provide some indication of the reason why it elects to do so:

...
XRE_main+0x00000058 [/usr/local/lib/firefox/libxul.so +0x03348aa7]
_start+0x00000825 [/usr/local/bin/firefox +0x00004935]
_start+0x00000c20 [/usr/local/bin/firefox +0x00004d30]
_start+0x0000008e [/usr/local/bin/firefox +0x0000419e]
UNKNOWN 0x800696000
[79233] ###!!! ABORT: Should be tracking any image we're going to use!: 'mImageTracked', file /usr/ports/www/firefox/work/mozilla-release/layout/style/nsStyleStruct.h, line 208
Hit MOZ_CRASH() at /usr/ports/www/firefox/work/mozilla-release/memory/mozalloc/mozalloc_abort.cpp:30


Can anybody who knows their way around the Firefox code look into this
further?

I myself am not at all familiar with the code base of Firefox.