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: | 26s - ActiveConfigAction's update | ||
---|---|---|---|
Product: | projects | Reporter: | _ ludo <ludo> |
Component: | Generic Infrastructure | Assignee: | Jesse Glick <jglick> |
Status: | RESOLVED FIXED | ||
Severity: | blocker | CC: | exceptions_reporter, ludo, vv159170 |
Priority: | P3 | ||
Version: | 6.x | ||
Hardware: | All | ||
OS: | All | ||
URL: | http://statistics.netbeans.org/exceptions/detail.do?id=157343 | ||
Issue Type: | DEFECT | Exception Reporter: | 157343 |
Description
_ ludo
2009-10-23 23:51:59 UTC
Most of the long calls seem to arrive from ActiveConfigAction (except bug 175416). It should probably reschedule its update outside of AWT thread. related to issue 172526 which sped things up a bit. There is no clear way to make it superfast. The uptimate slow process is reading the pom+all it's parents (can be like 5) and extract profiles from it. There's no other way to retrieve a list of profiles available. So the call to getConfigurations will eventually result in parsing/building/downloading parent pom files. Additionally the action wraps calls to the configuration provider into a read project mutex, increasing the likelihood of other things running to slow it down. I don't see however how the action's up could load the list up front and then somehow update it. any such tricks would just break macosx usage I think. Change of default owner. *** Bug 178487 has been marked as a duplicate of this bug. *** core-main #89b2bb5f3891 Integrated into 'main-golden', will be available in build *201004280200* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main/rev/ User: Log: *** Bug 170949 has been marked as a duplicate of this bug. *** |