From owner-freebsd-java@FreeBSD.ORG Thu Feb 2 15:04:18 2012 Return-Path: Delivered-To: java@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 06DCC106564A; Thu, 2 Feb 2012 15:04:18 +0000 (UTC) (envelope-from flo@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id E48698FC17; Thu, 2 Feb 2012 15:04:17 +0000 (UTC) Received: from bender.solomo.local (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q12F4G9Y020435; Thu, 2 Feb 2012 15:04:17 GMT (envelope-from flo@freebsd.org) Message-ID: <4F2AA5F0.3020507@freebsd.org> Date: Thu, 02 Feb 2012 16:04:16 +0100 From: Florian Smeets User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:10.0) Gecko/20120202 Thunderbird/10.0 MIME-Version: 1.0 To: Kevin Oberman References: In-Reply-To: X-Enigmail-Version: 1.3.5 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: java@freebsd.org, gecko@freebsd.org Subject: Re: Java (icedtea-weband openJDK6) crashes Firefox-10 X-BeenThere: freebsd-java@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting Java to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Feb 2012 15:04:18 -0000 On 02.02.2012 05:54, Kevin Oberman wrote: > Since the upgrade to firefox 10, it crashes when try to access the > puzzles at http://www/jigsawplanet.com. The puzzles are java and > worked fine under Firefox 9. The only other thing I normally run that > is in Java is the ICSI netalyzr, and it runs fine. Anyone else had a > problem like this? Hi, this seems to be a known problem with the icedtea-web plugin and firefox >= 10 :( Assertion failure: rt->onOwnerThread(), at /tmp/usr/ports/www/firefox/work/mozilla-release/js/src/jsapi.cpp:6316 Abort trap: 6 (core dumped) which is described here https://bugzilla.mozilla.org/show_bug.cgi?id=704249 More info: http://blog.mozilla.com/dmandelin/2011/11/22/js-newsletter-112-1122/ https://bugzilla.mozilla.org/show_bug.cgi?id=650411 I did not find a fix or workaround. Florian