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.
It greatly reduces the IDE responsiveness during opening of java file. Basically it invokes a java parser and waits for it to finish parsing, blocking AWT for nontrivial amount of time. Much more visible on multi-open.
Created attachment 14522 [details] Part of thread dump
The editor needs to know the fold information at the time when the file becomes visible. Not doing so will lead to flickering (in case the user has CF presets that some folds should be collapsed by default) and in fact it will be even slower overall because the views creation will be done twice. IMHO even if we would not query the CE due to folds the parsing would be done anyway as there are other tools inspecting SourceElement contents (NavigationView, beans etc.). I've added issues@java to cc so that they can comment on this. Thanks.
I presume that we will be able to improve this at least partially into promoD.
*** Issue 45094 has been marked as a duplicate of this issue. ***
This should now be fixed by integration of issue 42255. The folds are initialized lazily unless there is a code folding preset for certain fold type set to true. However there is still problem that the NavigationView in java module updates its content synchronously in AWT - see e.g. issue 41905. This can be eliminated by turning the editor toolbar off.
It's OK now.