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.
Summary: | Calling of TopComponent newInstance and readProperties via NBLifecycleManager.exit | ||
---|---|---|---|
Product: | platform | Reporter: | arittner <arittner> |
Component: | Window System | Assignee: | Stanislav Aubrecht <saubrecht> |
Status: | NEW --- | ||
Severity: | normal | CC: | jtulach |
Priority: | P3 | ||
Version: | 8.0 | ||
Hardware: | PC | ||
OS: | Windows 7 | ||
Issue Type: | DEFECT | Exception Reporter: |
Description
arittner
2014-05-05 08:25:12 UTC
Oh dear, isExiting() is not declared in the interface LifecycleManager. It's a static method in NbLifecycleManager. So, no workaround... Yeah, I don't see a reason why components not yet in memory should be loaded on system exit. The bug however needs to be handled in window system. A traditional workaround is to have own ModuleInstall.closing method and when it returns true, remember that the system is likely shutting down. IMHO another sideeffect on this bug: http://forums.netbeans.org/viewtopic.php?p=163668 Is it possible to take a look on this? This problem hits me too. In my application some top components are heavy, and it takes some time to initialize. Because of this bug closing the application takes way longer than it should. Ancient but vaguely related: https://netbeans.org/bugzilla/show_bug.cgi?id=28960 (In reply to Jaroslav Tulach from comment #2) > Yeah, I don't see a reason why components not yet in memory should be loaded > on system exit. The bug however needs to be handled in window system. > > A traditional workaround is to have own ModuleInstall.closing method and > when it returns true, remember that the system is likely shutting down. Yes, but you need a ModuleInstall or @OnStop Hook in any modul to catch the current shutdown state. So you spreed the "workaround"/"hack" in hundred of modules and add in hundred of TopComponents a "isShutDown" query... :-/ Some additional side effects: Not only the <init> constructors from TopComponents are called. After that the shutdown process calls any writeProperties method. This may bring more problems. |