From owner-freebsd-gecko@freebsd.org  Sun Mar 13 21:23:07 2016
Return-Path: <owner-freebsd-gecko@freebsd.org>
Delivered-To: freebsd-gecko@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8176AACE0D7
 for <freebsd-gecko@mailman.ysv.freebsd.org>;
 Sun, 13 Mar 2016 21:23:07 +0000 (UTC) (envelope-from pi@FreeBSD.org)
Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org
 [IPv6:2001:1900:2254:206a::50:5])
 by mx1.freebsd.org (Postfix) with ESMTP id 71EA4199D
 for <freebsd-gecko@freebsd.org>; Sun, 13 Mar 2016 21:23:07 +0000 (UTC)
 (envelope-from pi@FreeBSD.org)
Received: by mailman.ysv.freebsd.org (Postfix)
 id 6D9CBACE0D6; Sun, 13 Mar 2016 21:23:07 +0000 (UTC)
Delivered-To: gecko@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6D2E1ACE0D5
 for <gecko@mailman.ysv.freebsd.org>; Sun, 13 Mar 2016 21:23:07 +0000 (UTC)
 (envelope-from pi@FreeBSD.org)
Received: from fc.opsec.eu (fc.opsec.eu [IPv6:2001:14f8:200:4::4])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 32463199C;
 Sun, 13 Mar 2016 21:23:07 +0000 (UTC) (envelope-from pi@FreeBSD.org)
Received: from pi by fc.opsec.eu with local (Exim 4.86_2 (FreeBSD))
 (envelope-from <pi@FreeBSD.org>)
 id 1afDTX-000LNv-JA; Sun, 13 Mar 2016 22:22:59 +0100
Date: Sun, 13 Mar 2016 22:22:59 +0100
From: Kurt Jaeger <pi@FreeBSD.org>
To: Jan Beich <jbeich@FreeBSD.org>
Cc: Kurt Jaeger <pi@FreeBSD.org>, gecko@freebsd.org
Subject: Re: firefox 45.0 (latest build) hangs, what kind of trace helps ?
Message-ID: <20160313212259.GR991@fc.opsec.eu>
References: <20160313160121.GP991@fc.opsec.eu> <fuvu-2sbc-wny@vfemail.net>
 <shzu-z1r3-wny@vfemail.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <shzu-z1r3-wny@vfemail.net>
X-BeenThere: freebsd-gecko@freebsd.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: Gecko Rendering Engine issues <freebsd-gecko.freebsd.org>
List-Unsubscribe: <https://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: <https://lists.freebsd.org/mailman/listinfo/freebsd-gecko>,
 <mailto:freebsd-gecko-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 13 Mar 2016 21:23:07 -0000

Hi!

> These steps are actually a wild goose chase. Firefox issues are way
> easier to track down as regressions by eliminating differences between
> working and non-working version.

Ok.

> The first candidate is always the
> fragile user environment, so you need to start from a clean slate by
> populating a jail with X11 pass-through and trying to reproduce there.

Thanks for the warning.

It happens in heavy use with many open windows after approx. 24h
and if I setup a test-only environment, it'll be difficult to reproduce.

I'll see what I can do. Thanks for the tips!

-- 
pi@FreeBSD.org         +49 171 3101372                4 years to go !