This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Summary: | AWT thread blocked for 30484 ms. | ||
---|---|---|---|
Product: | javafx | Reporter: | emcmanus <emcmanus> |
Component: | Editor | Assignee: | J Bachorik <yardus> |
Status: | VERIFIED FIXED | ||
Severity: | normal | CC: | bondolo, sunflower, yardus |
Priority: | P2 | Keywords: | PERFORMANCE |
Version: | 6.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: | 163706 |
Attachments: |
nps snapshot
nps snapshot nps snapshot nps snapshot nps snapshot nps snapshot IDE Thread Dump |
Description
emcmanus
2009-12-16 14:04:33 UTC
Created attachment 92685 [details]
nps snapshot
Created attachment 92995 [details]
nps snapshot
Created attachment 93198 [details]
nps snapshot
project string search
Created attachment 93199 [details]
nps snapshot
When listing an unexpanded packet, sometimes it responses so slowly.
Created attachment 93795 [details]
nps snapshot
I downloaded the JavaFX Runtime, opened the javafx-ui-control project and used Go To Source action
Created attachment 93796 [details]
nps snapshot
I downloaded the JavaFX SDK Runtime and opened the javafx-ui-controls, created a JavaFX class and tried to rename the class name.
refactoring - yardus Was addressed by http://hg.netbeans.org/javafx/rev/85a382840aaf unable to reproduce in build NetBeans-JavaFX-Soma: #200 Is this really fixed?. I see this all the time while I'm working using JavaFX (6.9 beta). When I click on the explorer node to bring up the context menu it takes up to 5 secs to popup. A little window at the bottom always asks me to report it. I'm keep reporting it. This is very counter productive. Some steps to reproduce - Open a large JavaFX project (Note, my project has about 80 JavaFX classes) - Open a particular JavaFX file - Do some modification and Save - Immediately right click on the same file node in the project explorer Notice the context menuu takes several seconds to open. The delay is really prominent if you see "scanning the project.." at the status bar. Winston, I think you are really talking about #178754. It has just been fixed, FYI. Please, ignore the issue number in the last comment. Bugzilla is playing tricks with me. The number I was to mention was #183968 I tried to play with it and my IDE hangs for some time. The Thread Dump is attached. It is different form the issue 183968. But probably it could be another known issue. Created attachment 97780 [details]
IDE Thread Dump
"AWT-EventQueue-1" prio=6 tid=0x03f4b400 nid=0x7c8 runnable [0x0566e000] java.lang.Thread.State: RUNNABLE at java.util.zip.Deflater.deflateBytes(Native Method) at java.util.zip.Deflater.deflate(Deflater.java:290) - locked <0x15e7c2e0> (a java.util.zip.Deflater) at java.util.zip.DeflaterOutputStream.deflate(DeflaterOutputStream.java:159) at java.util.zip.DeflaterOutputStream.write(DeflaterOutputStream.java:118) at java.util.zip.GZIPOutputStream.write(GZIPOutputStream.java:72) - locked <0x15e8c318> (a java.util.zip.GZIPOutputStream) at java.io.ObjectOutputStream$BlockDataOutputStream.drain(ObjectOutputStream.java:1838) at java.io.ObjectOutputStream$BlockDataOutputStream.setBlockDataMode(ObjectOutputStream.java:1747) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1161) at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:326) at java.util.TreeMap.writeObject(TreeMap.java:2252) at sun.reflect.GeneratedMethodAccessor147.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) The last stacktrace just shows the self-sampler engine going astray. AFAIK, it is a known problem in NB and it is being worked on right now. I got the issue in the latest build NetBeans-JavaFX-Soma: #228 (Apr 21, 2010 12:01:48 AM) verified in netbeans-trunk-nightly-201005182201-javafx-windows.exe |