This bug was originally marked as duplicate of bug 181584, that is already resolved. This bug is still valid, so this seems to be another bug, but it might be related.
Build: NetBeans IDE 7.0 Beta (Build 201011152355)
VM: Java HotSpot(TM) 64-Bit Server VM, 17.0-b16, Java(TM) SE Runtime Environment, 1.6.0_21-b06
scotth1: editing a JSF 2.0 facelets client page.
and was waiting for list of tags.
Maximum slowness yet reported was 3931 ms, average is 3931
Created attachment 105833 [details]
OK so I tried to quickly evaluate all snapshots 7.0 a newer (last evaluated number was 512503).
Most of the snapshots were broken, some of them seems to not be caused by NB and the rest is in the category "could be valid" but I don't evaluate it for longer time if I saw that it should be another area.
broken snapshots: 512503, 510102, 511279, 512503, 511896, 511137, 510748, 510741, 479982
not NB related/extra slow native calls: 510770, 511784, 512265, 511461, 511229
could be valid: 510400, 511382, 511299(JSP), 510410(JSF)
The original snapshot for JSF editor was badly uploaded as well. For the second JSF report I entered issue #199110. I'm reassigning this issue to JSP for evaluation of 511299.
broken npss: 512613, 512705, 513065, 513619, 513265, 513491, 513829, 514051, 514194, 514244
not NB issues (slow java2d call): 512624, 513541
There is no valid profiler snapshot from the last 10 days. All mentioned snapshots are broken or NetBeans unrelated. Last investigated nps was 514244.
I entered new issue #199371 for the JSP problems so this issue became stack of invalid and mostly broken exception reports. More than 50-60% of all attached snapshots are broken, perhaps cancelled by users. More than 85% of new snapshots from last 10 days were broken. Perhaps would be good to implement some filter for broken snapshots.
BTW, valid JSP, JSF troubles were separated so I'm closing this one.
Problem still exist in current nightly build, sometimes up to more than 20 seconds.
muellermi can you please specify which what is slow? Especially your troubles seems to be perhaps related to JDK. It's suspicious that most of sun.java2d slownesses are under JDK 1.6 build 26. Please try to switch to another one, it should help.
Most of reports looks broken again or not directly nb related. Really roughly investigated...
broken snapshot: 516037, 515930, 515888, 515822, 515758, 515744, 515732, 515609, 515386, 515308, 515284, 514925, 514857
slow swing call: 514319
slow zipfile native calls by scanning: 515048
perhaps lack of resources: 515090
slow sun.java2d native call: 515764, 515697, 515695, 515470, 515467, 514834, 514328
I'm moving that to product Platform... could somebody evaluate mentioned sun.java2d calls? Is it possible to do with that anything? Perhaps feel free to close that as wontfix (I don't see actually way how to improve that). Thanks.
In addition I will increase priority for filtering out broken snapshots since its more than 50% of this issue (see issue #199372).
the slow native calls are in sun.java2d.windows.GDIBlitLoops.nativeBlit.
so it's either a bug in graphics driver or in JDK or both. cannot be fixed in netbeans.
try updating graphics driver and/or some other JDK update
I hope JavaFX 2.0 can save us from this neverending GUI bugs...
*** Bug 201138 has been marked as a duplicate of this bug. ***
is there a java bug on slow nativeBlit?
*** Bug 231830 has been marked as a duplicate of this bug. ***
*** Bug 232503 has been marked as a duplicate of this bug. ***
*** Bug 236986 has been marked as a duplicate of this bug. ***
reports are still coming in, reassigning to jdk problems - is there a jdk bug filed for this? If not it should be filed.
According to recent reports this looks like a duplicate of java bug #6477756
*** This bug has been marked as a duplicate of bug 227232 ***
*** Bug 239597 has been marked as a duplicate of this bug. ***
*** Bug 247972 has been marked as a duplicate of this bug. ***
*** Bug 252181 has been marked as a duplicate of this bug. ***
*** Bug 258561 has been marked as a duplicate of this bug. ***
*** Bug 257847 has been marked as a duplicate of this bug. ***