From owner-freebsd-gecko@FreeBSD.ORG Mon May 19 18:51:24 2014 Return-Path: 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 EF701B2C; Mon, 19 May 2014 18:51:24 +0000 (UTC) Received: from outgoing.tristatelogic.com (segfault.tristatelogic.com [69.62.255.118]) by mx1.freebsd.org (Postfix) with ESMTP id D7C6F2A30; Mon, 19 May 2014 18:51:24 +0000 (UTC) Received: from segfault-nmh-helo.tristatelogic.com (localhost [127.0.0.1]) by segfault.tristatelogic.com (Postfix) with ESMTP id F15393ACCF; Mon, 19 May 2014 11:51:23 -0700 (PDT) From: "Ronald F. Guilmette" Subject: Re: firefox-29.0,1 -- dumps core In-Reply-To: Date: Mon, 19 May 2014 11:51:23 -0700 Message-ID: <64284.1400525483@server1.tristatelogic.com> Cc: gecko@freebsd.org, FreeBSD Ports ML X-BeenThere: freebsd-gecko@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Gecko Rendering Engine issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 May 2014 18:51:25 -0000 In message Kevin Oberman wrote: >No problems with www.newegg.com. Works fine for me. Two questions: 1) Are you running on an AMD platform? 2) When you ran your test, did you first rebuild & reinstall Firefox with these two build options enabled? DEBUG -- Build with debugging support LOGGING -- Additional log messages (I built mine with these options, and I do believe that it may indeed make a world of difference as to whether or not you will experience the crashes in firefox that I have described.)