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.
Regression in today's dev build, I think caused by the new animated icon for the Java parse status. Mustang b45 / Linux / Gnome. Start IDE and wait for CP scanning etc. to finish. CPU usage is zero. Open any Java file and wait for it parse. Zero again. Now press Space and Ctrl-Z to force a reparse, so that the animated icon appears and then goes back to a green square. Now you have 100% CPU usage. Closing the file does not help; you have to restart the IDE. But of course *any* realistic IDE session involves editing some Java file, so every IDE session consumes 100% of my CPU -> P1 at least for me. Leaving P2 in case it does not happen to everyone; maybe a JDK bug?
Created attachment 24097 [details] Some thread dumps; note "Image Animator 0" thread, only present after parsing a Java file
Seems that it was already fixed in CVS (and I can confirm that the change does indeed fix my problem). So please don't change it back! :-) Date: 2005/08/19 22:09:44 Author: jlahoda Log: Removing animation from the clocks icon (should help to solve problems with commit validation). editor/errorstripe/src/org/netbeans/modules/editor/errorstripe/resources/hodiny.gif:1.1->1.2
I will re-implement the animation by hand (once I will got a bit time), I hope it will be possible.
Well, is the animation really necessary. It will unnecessarily slow down the parsing in any case.
Moving to the ui category.