10 messages in net.java.dev.scenegraph.devRe: Runtime issues| From | Sent On | Attachments |
|---|---|---|
| Alexandr Scherbatiy | Jul 8, 2008 3:15 am | |
| Brent Christian | Jul 8, 2008 11:52 am | |
| Shannon Hickey | Jul 8, 2008 12:34 pm | |
| Jim Graham | Jul 8, 2008 12:59 pm | |
| Shannon Hickey | Jul 8, 2008 1:14 pm | |
| Brent Christian | Jul 8, 2008 1:43 pm | |
| Jim Graham | Jul 8, 2008 2:26 pm | |
| Kevin Rushforth | Jul 9, 2008 2:00 pm | |
| Alexandr Scherbatiy | Jul 10, 2008 6:27 am | |
| Kevin Rushforth | Jul 10, 2008 7:59 am |
| Subject: | Re: Runtime issues | |
|---|---|---|
| From: | Alexandr Scherbatiy (Alex...@Sun.COM) | |
| Date: | Jul 10, 2008 6:27:11 am | |
| List: | net.java.dev.scenegraph.dev | |
Kevin Rushforth wrote:
Is http://openjfx.java.sun.com/jira/browse/JFXC-1471 considered a stopper for the preview release? Sounds pretty serious if it happens every time an applet is stopped. Plus it's a fairly new regression.
It is a highly visible regression for the NetBeans JavaFX Script plugin because it appears every time when disabling or resetting a Preview panel. See http://www.netbeans.org/issues/show_bug.cgi?id=139363
If it is a stopper, then it's priority should be bumped up in JIRA.
Which priority should be be set for the issue in this case?
Thanks, Alexandr.
-- Kevin
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 - which is probably Igor.
Meanwhile, Brent - you might want to reevaluate if you still want that printStackTrace in the LongSleepingThread...
...jim
Shannon Hickey wrote:
I've assigned both issues to Jim Graham. Is he the right person to own them or is Igor?
Thanks, Shannon
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
Alexandr Scherbatiy wrote:
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.
Andrey.