From owner-freebsd-java@FreeBSD.ORG Thu Mar 4 05:37:25 2004 Return-Path: Delivered-To: freebsd-java@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3995E16A4CF for ; Thu, 4 Mar 2004 05:37:25 -0800 (PST) Received: from Shenton.org (23.ebbed1.client.atlantech.net [209.190.235.35]) by mx1.FreeBSD.org (Postfix) with SMTP id 48F7E43D45 for ; Thu, 4 Mar 2004 05:37:24 -0800 (PST) (envelope-from chris@Shenton.Org) Received: (qmail 61312 invoked by uid 1001); 4 Mar 2004 13:37:23 -0000 To: "Georg-W. Koltermann" References: <1078359013.1369.22.camel@localhost.muc.eu.mscsoftware.com> From: Chris Shenton Date: Thu, 04 Mar 2004 08:37:23 -0500 In-Reply-To: <1078359013.1369.22.camel@localhost.muc.eu.mscsoftware.com> (Georg-W. Koltermann's message of "Thu, 04 Mar 2004 01:10:13 +0100") Message-ID: <864qt4wx64.fsf@PECTOPAH.shenton.org> User-Agent: Gnus/5.110002 (No Gnus v0.2) Emacs/21.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii cc: freebsd-gnats-submit@FreeBSD.org cc: freebsd-java@freebsd.org Subject: Re: ports/63409: jdk-1.4.2p6_3 plugin crashes Mozilla-1.6_2,2 X-BeenThere: freebsd-java@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting Java to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Mar 2004 13:37:25 -0000 "Georg-W. Koltermann" writes: > Well know, seen before, fixed. See the thread at > http://www.freebsd.org/cgi/getmsg.cgi?fetch=183044+0+/usr/local/www/db/text/2004/freebsd-java/20040125.freebsd-java > > This *is* in fact a jdk14 problem, please reassign back. Oddly, I poked at the applet a couple times after this, got various failures, then it eventually worked. No changes on my end, just returning to the same web page, clicking the same applet. Like there were problems initializing them vm the first time then "fixed themselves" :-( on subsequent invocations. Should I close the ticket? The behavior's a bit flaky, but I was able to get beyond the initial problem -- though it's not "fixed".