From owner-freebsd-java Wed Feb 11 13:05:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA20554 for java-outgoing; Wed, 11 Feb 1998 13:05:49 -0800 (PST) (envelope-from owner-freebsd-java@FreeBSD.ORG) Received: from corp.tivoli.com (corp.tivoli.com [146.84.1.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA20547 for ; Wed, 11 Feb 1998 13:05:47 -0800 (PST) (envelope-from ebrunett@dev.tivoli.com) Received: from kenya.dev.tivoli.com (kenya.dev.tivoli.com [146.84.26.101]) by corp.tivoli.com (8.8.7/8.8.7) with ESMTP id PAA05287; Wed, 11 Feb 1998 15:03:29 -0600 (CST) Received: (from ebrunett@localhost) by kenya.dev.tivoli.com (8.8.8/8.8.8) id PAA18635; Wed, 11 Feb 1998 15:05:14 -0600 (CST) Date: Wed, 11 Feb 1998 15:05:14 -0600 (CST) Message-Id: <199802112105.PAA18635@kenya.dev.tivoli.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit From: Enrico Brunetta To: "Patrick Murphy" Cc: "FreeBSD Java Mail List" Subject: Re: Problem in latest release In-Reply-To: <199802111954.OAA48084@pilot001.cl.msu.edu> References: <199802111954.OAA48084@pilot001.cl.msu.edu> X-Mailer: VM 6.22 under 19.15 XEmacs Lucid Sender: owner-freebsd-java@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Patrick, This is exactly the same problem I've been experiencing in the past (even before this release). Note that I am also running all my java apps on a remote X server (because my FreeBSD box doesn't have a graphics card). Unfortunately, I cannot reproduce this in a consistent way. It happens more often when I crazy-click(tm) my Swing app. On a related note, if I run all my swing apps using Alex Boisvert's jdk1.1.2 (ftp://ftp.freebsd.org/pub/FreeBSD/incoming/jdk1.1.2-fbsd1.tgz.good) not only I do not get this error, but all my apps run at a much better speed (almost twice as fast!!). Alex, if you are on this list, maybe you can see what are the main differences in implementing the VM code between your version and Nate's 1.1.5 ? Enrico. Patrick Murphy (murphyp1@pilot.msu.edu) wrote on Feb 11, 1998 14:54: >I just installed the latest version of java marked >"jdk1.1.5-FreeBSD:1998/02/08". I was able to run the CaffeineMark 3.0 test >against the prior release without a problem. Against this release from a >remote x server I am getting the following abort in 5 out of 6 runs: > >assertion "mid->pendingq == SYS_MID_NULL" failed: file >"../../../../src/freebsd/java/green_threads/src/signals.c", line 444 >SIGABRT 6* abort (generated by abort(3) routine) > >Full thread dump: > "Thread-6" (TID:0x8611918, sys_thread_t:0x9490efc, state:MW) prio=5 > CaffeineMarkFrame.drawTestResult(CaffeineMarkFrame.java) > CaffeineMarkFrame.paint(CaffeineMarkFrame.java) > CaffeineMarkFrame.status(CaffeineMarkFrame.java) > CaffeineMarkBenchmark.run(CaffeineMarkBenchmark.java) > "AWT-Finalizer" (TID:0x86113c0, sys_thread_t:0x94d2efc, state:CW) prio=9 > java.lang.Object.wait(Object.java) > sun.awt.AWTFinalizer.run(AWTFinalizer.java:48) > "Screen Updater" (TID:0x8610b38, sys_thread_t:0x94b1efc, state:CW) >prio=4 > java.lang.Object.wait(Object.java) > sun.awt.ScreenUpdater.nextEntry(ScreenUpdater.java:78) > sun.awt.ScreenUpdater.run(ScreenUpdater.java:98) > "AWT-Motif" (TID:0x860d1b0, sys_thread_t:0x946fefc, state:CW) prio=5 > java.lang.Thread.run(Thread.java) > "AWT-Input" (TID:0x860d1d0, sys_thread_t:0x944eefc, state:CW) prio=5 > "AWT-EventQueue-0" (TID:0x860d1e8, sys_thread_t:0x942defc, state:R) >prio=5 *current thread* > sun.awt.motif.X11Graphics.setFont(X11Graphics.java:125) > CaffeineMarkFrame.drawTestResult(CaffeineMarkFrame.java) > CaffeineMarkFrame.paint(CaffeineMarkFrame.java) > java.awt.Component.dispatchEventImpl(Component.java:1723) > java.awt.Container.dispatchEventImpl(Container.java:939) > java.awt.Window.dispatchEventImpl(Window.java:443) > java.awt.Component.dispatchEvent(Component.java:1704) > java.awt.EventDispatchThread.run(EventDispatchThread.java:63) > "Finalizer thread" (TID:0x860bc50, sys_thread_t:0x940cefc, state:CW) >prio=1 > "Async Garbage Collector" (TID:0x860bc98, sys_thread_t:0x93ebefc, >state:CW) prio=1 > "Idle thread" (TID:0x860bb88, sys_thread_t:0x93caefc, state:R) prio=0 > "Clock" (TID:0x8608088, sys_thread_t:0x93a9efc, state:CW) prio=12 > "main" (TID:0x86080b0, sys_thread_t:0xf3c00, state:CW) prio=5 >Monitor Cache Dump: > sun.awt.AWTFinalizer@86113C0/8662C20: > Waiting to be notified: > "AWT-Finalizer" (0x94d2efc) > sun.awt.motif.MToolkit@860D268/8664C68: owner "AWT-EventQueue-0" >(0x942defc, 1 entry) > Waiting to enter: > "Thread-6" (0x9490efc) > Waiting to be notified: > "AWT-Motif" (0x946fefc) > (0x93ebefc): > Waiting to be notified: > "Async Garbage Collector" (0x93ebefc) > sun.awt.ScreenUpdater@8610B38/869B5A8: > Waiting to be notified: > "Screen Updater" (0x94b1efc) >Registered Monitor Dump: > Thread queue lock: > Waiting to be notified: > "main" (0xf3c00) > Name and type hash table lock: > String intern lock: > JNI pinning lock: > JNI global reference lock: > BinClass lock: > Class loading lock: > Java stack lock: > Code rewrite lock: > Heap lock: > Has finalization queue lock: > Finalize me queue lock: > Waiting to be notified: > "Finalizer thread" (0x940cefc) > Monitor IO lock: > Child death monitor: > Event monitor: > I/O monitor: > Waiting to be notified: > "AWT-Input" (0x944eefc) > Alarm monitor: > Waiting to be notified: > "Clock" (0x93a9efc) > _malloc: > Monitor registry: owner "AWT-EventQueue-0" (0x942defc, 1 entry) >Thread Alarm Q: > sys_thread_t 0x946fefc [Timeout in 10 ms] > sys_thread_t 0x944eefc [Timeout in 158 ms] > sys_thread_t 0x93ebefc [Timeout in 367 ms] > >This abort does not seem to be happening on a local x server. I do have a >java.core file from the abort if it would help. > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe java" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe java" in the body of the message