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: | Slow IDE shutdown | ||
---|---|---|---|
Product: | projects | Reporter: | _ rkubacki <rkubacki> |
Component: | Generic Infrastructure | Assignee: | Milos Kleint <mkleint> |
Status: | RESOLVED WONTFIX | ||
Severity: | blocker | CC: | issues, tzezula |
Priority: | P3 | Keywords: | PERFORMANCE |
Version: | 6.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: | |
Attachments: | thread dump |
Description
_ rkubacki
2007-03-09 15:17:45 UTC
Created attachment 39341 [details]
thread dump
It should be solved by the project infrastructure. The same holds for opening projects when the classpaths are randomly registered in the GPR and events are fired from it. The project system should register the classpaths at once when all depending projects are opened and the same holds for ide closing. Do you mean that we should do event coalscing on startup and shutdown Tomas? Will this help? The better approach is to create a support which allows registering and unregistering at once with one event. Currently also the RepositoryUpdater has problem wih events from GPR. Naive synchronous implementation which reacts on each event was unusable, only collecting of classpaths in case of nbbuild took about 10 minutes. The RepositoryUpdater is now a sliding task, but it makes quite hard to implement determinate progress of background scanning. that would mean cutting GlobalPathRegistry.getDefault().register() calls from the ProjectOpenedHook implementations, right? I will stop pretending this is going to happen any time soon -> LATER. please reopen/escalate when critical NetBeans.org Migration: changing resolution from LATER to WONTFIX |