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.
Shows up as a big time hit in a profiler during shutdown, esp. w/ lookup caching enabled which otherwise avoids parsing most .settings during rest of IDE session. Current impl finds every instance in Services (folder traversal) and asks it if it is instanceOf whatever option. getCookie(InstanceCookie.class) is the major time drain: causes parsing of XML. Better to somehow "remember" where an option came from; perhaps some secret property in SystemOption.
In age of nb<3.2 some SOs (debugger?) relied on the fact that the projects infra. writes down all SOs when closing a project. Since it was not part of any public contract, maybe it could be removed entirely now. nb 4.0 will provide the api to allow to track opening and closing of projects.
Target milestone marked 4.0, According to Jan there should be replacement for this strange way how to track projects opening.
Looks like settings issue.
FYI doing this may also force classloading on shutdown. I've noticed the CORBA module getting a bunch of its classes suddenly loaded during IDE shutdown, when running with verbose gc.
Tonda, this might be of interest for you. However I do not know if you track also shutdown of app.
So I guess this won't get addressed for 4.0. TM should be updated.
This is no longer a problem in 4.1. There is no XMLsettingsHandler now. What I see as a biggest trouble in current shutdown is saving of winsys + persisting of MDR data. Saving of winsys is related to settings and there are bugs for this problem but probably needs to be fixed at a different place.
i agree, closing this.