atom feed10 messages in net.java.dev.scenegraph.devRe: Runtime issues
FromSent OnAttachments
Alexandr ScherbatiyJul 8, 2008 3:15 am 
Brent ChristianJul 8, 2008 11:52 am 
Shannon HickeyJul 8, 2008 12:34 pm 
Jim GrahamJul 8, 2008 12:59 pm 
Shannon HickeyJul 8, 2008 1:14 pm 
Brent ChristianJul 8, 2008 1:43 pm 
Jim GrahamJul 8, 2008 2:26 pm 
Kevin RushforthJul 9, 2008 2:00 pm 
Alexandr ScherbatiyJul 10, 2008 6:27 am 
Kevin RushforthJul 10, 2008 7:59 am 
Subject:Re: Runtime issues
From:Jim Graham (Jim.@Sun.COM)
Date:Jul 8, 2008 2:26:58 pm
List:net.java.dev.scenegraph.dev

Or at least test "if this is one of the 'expected' Interrupts then let's eat the stack trace" - if that is something we can test...

...jim

Brent Christian wrote:

Jim Graham wrote:

I would think Igor by default. The "MasterTimer" in the thread stack trace in one of the reports was a red herring I think - it looks like Brent left in a printStackTrace() for the new LongSleepingThread that he created to deal with hires timers recently, so that part is probably harmless. The real issue seems to be the IMSE that gets thrown

I came to the same conclusion.

Meanwhile, Brent - you might want to reevaluate if you still want that printStackTrace in the LongSleepingThread...

Sure. I'm not a big fan of ignoring exceptions, but it does seem harmless in this case. I would think we can roll that change into the rest of the resolution for 1471.

-Brent

I've assigned both issues to Jim Graham. Is he the right person to own them or is Igor?

Brent Christian wrote:

Hi, Alexandr

I agree that these two issues appear to originate in scenegraph code. I know Igor Kushnirskiy was looking into running scenegraph in the applet case, and he's also familiar with scenegraph's use of the java.util.concurrent APIs. He should be back from vacation tomorrow.

It's worth noting that the runtime has not been using the very latest scenegraph bits, and is missing a few fixes, though I don't think they are changes that will effect these issues. The next runtime build should be up-to-date wrt scenegraph.

I noticed that the JFXC-948 thread dump is from JRE 1.6.0_05. Was JFXC-1471 also running under 1.6.0_05? I would be interested to know if the new plugin in 6u10 makes any difference.

Thanks, -Brent

Are these issue from scenegraph?

--------------------------------------------------------------------- JFXC-948 http://openjfx.java.sun.com/jira/browse/JFXC-948 "AWT-EventQueue-6" prio=4 tid=0x099d4000 nid=0xcc in Object.wait() [0x0badf000..0x0badfd14] java.lang.Thread.State: WAITING (on object monitor) at java.lang.Object.wait(Native Method) at java.lang.Object.wait(Object.java:485) at java.awt.EventQueue.getNextEvent(Unknown Source) - locked <0x230c30e8> (a com.sun.scenario.scenegraph.SGEventQueue) at com.sun.scenario.scenegraph.SGEventQueue.getNextEvent(SGEventQueue.java:447)

at com.sun.scenario.scenegraph.SGEventQueue.getNextEvent(SGEventQueue.java:467)

at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source) at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source) at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source) at java.awt.EventDispatchThread.pumpEvents(Unknown Source) at java.awt.EventDispatchThread.pumpEvents(Unknown Source) at java.awt.EventDispatchThread.run(Unknown Source)

--------------------------------------------------------------------- JFXC-1471 http://openjfx.java.sun.com/jira/browse/JFXC-1471

java.lang.InterruptedException: sleep interrupted at java.lang.Thread.sleep(Native Method) at com.sun.scenario.animation.MasterTimer$LongSleepingThread.run(MasterTimer.java:71)

Exception in thread "pool-7-thread-1" java.lang.IllegalMonitorStateException at java.util.concurrent.locks.ReentrantLock$Sync.tryRelease(Unknown Source) at java.util.concurrent.locks.AbstractQueuedSynchronizer.release(Unknown Source) at java.util.concurrent.locks.ReentrantLock.unlock(Unknown Source) at java.util.concurrent.DelayQueue.take(Unknown Source) at java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(Unknown Source) at java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.getTask(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source)

Thanks, Alexandr.

Andrey Yamkovoy wrote:

Hi! We have the following issues in the runtime which affects preview functionality of the NetBeans plugin: JFXC-948 <http://openjfx.java.sun.com/jira/browse/JFXC-948> Timeline in applet does not start for second time JFXC-1471 <http://openjfx.java.sun.com/jira/browse/JFXC-1471> IllegalMonitorStateException in Applet

Moreover the 2nd one is a regression from 3-5 days old build. Could you please evaluate these issues.