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.
This bug was originally marked as duplicate of bug 192316, 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 2 (Build 201102111519) VM: Java HotSpot(TM) 64-Bit Server VM, 17.1-b03-307, Java(TM) SE Runtime Environment, 1.6.0_22-b04-307-10M3261 OS: Mac OS X User Comments: GUEST: NetBeans 7.0 beta start up michal.owsiak: Opening NetBeans with WebApplication project opened and more than 10 files in editor. Maximum slowness yet reported was 4422 ms, average is 3793
Created attachment 106091 [details] nps snapshot
The snapshots from Exception reporter shows, that majority of the code folding computation is done in the Java Folding support. But again most part of Java Folding originates from classloading - I assume the perf problem was captured during IDE startup. The referenced maybe-duplicate even specifically talks about startup process. It seems that # of files in editor does not have observable effect on the issue (see exception reports) It *might* visually help to move the folding initialization from AWT thread to a request processor, but the referenced classes must be loaded and initialized anyway, so I do not expect noticeable overall performance benefit. Closing as WONTFIX. Can be reopened, if it is decided that moving off AWT thread itself is worth the change.
I'm having this if I keep focus on the IDE. If not I get this issue: https://netbeans.org/bugzilla/show_bug.cgi?id=204624 Maybe worth looking at.
Start NetBeans from the commandline (run 'cmd'), adjust your console window propeties to have infinite (or very large) scrollback buffer, then press Ctrl-Break upon freeze and save the output. http://wiki.netbeans.org/GenerateThreadDump
No further input; closing.