Performance whitelist test reports that the following classes are being loaded on NetBeans startup:
This is considered as NetBeans performance regression. Please remove these classes from NetBeans startup.
This issue is based on jtulach's comment:
Report a bug for the module to switch to new declarative actions
(Actions.alwaysEnabled or TopComponent.openAction)
Created attachment 64742 [details]
org.netbeans.modules.java.hints.analyzer.OverridePreferences is likely to be bug in the test itself - this class is
referenced only from a method body, and is likely to be loaded through the class/bytecode verifier. Given that the
verifier is disabled in release builds, this class should not be reported, IMO.
To eliminate org.netbeans.modules.java.hints.analyzer.AnalyzeFolder$ToolsAction, we would need to make this action
enabled all the time, which is not very appropriate, IMO.
We could save org.netbeans.modules.java.hints.analyzer.AnalyzeFolder why shuffling the code a bit, but I am not sure if
it is worth the effort.
Jardo, any opinion? Thanks.
Any progress in this one?
According to the rules, I should close issues, that are INCOMPLETE for more than 4 weeks.
But in this case, I don't feel like the person that should decide about closing...
So please, can anyone competent decide, wheter this is going to be started, or wontfix ... or anything else :)
Should be fixed ot wontfixed in 7.0
No comments from yarda, not such an import issue to load one class imho => WONTFIX, sorry.
Reopening to fix.
When fixing other class blacklist related bugs, please add the class names into ide.kit/**/blacklist.txt yourself and
re-run the GeneralSanityTest. That will help you verify the bug is fixed. Done in ergonomics#c45e9c6c96fa
Integrated into 'main-golden', will be available in build *200910151401* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)
User: Jaroslav Tulach <firstname.lastname@example.org>
Log: #140390: Verifying no analyzer classes are loading during start
These classes still seem to be loaded. There is no way to avoid it, as the action is registered as ToolsAction and there is no way to register a declarative action into ToolsAction right now.
Removing the action from blacklist for now: ergonomics#f94d7604859f
No idea why this bug has been re-opened. This bug was considered to be won't fix, to my knowledge (there is no entry about any fix, only jtulach's commit that includes the classes into the blacklist, without any real fix). Jarda, please resolve somehow (or I will won't fix it myself).
As the action seems to be mostly enabled on java packages in projects view, consider registering it in their popup menu only. Otherwise please employ context sensitivity as enabled by bug 180979.
Unlikely I will be able to work on this in the foreseeable future.