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.
Build: NetBeans IDE 7.3 (Build 201302132200) VM: Java HotSpot(TM) 64-Bit Server VM, 23.6-b04, Java(TM) SE Runtime Environment, 1.7.0_11-b21 OS: Windows 7 User Comments: rptmaestro: Renaming files GUEST: NetBeans was downloading and unpacking maven indexes from a corporate Nexus repository. Desktop freezes each time it does so. Maximum slowness yet reported was 76660 ms, average is 42767
Created attachment 135469 [details] nps snapshot
most likely un-opened maven projects are affecting these slowdown. For opened projects, we are hardreferencing MavenProject instance, so once loaded it never gets released. given that it's almost always necessary that's correct. For unopened projects, we only softReference the instance, so at times of reaching the memory limit, the MavenProject instances are cleared. The stacktraces in the snapshots demonstrate it, at least in one case the code above the slow stacktrace did use MavenProject as well but was fast. There is no real solution to the problem, use primarily only opened projects, limit the number of opened projects and/or increase heap size to prevent dropping MavenProject instances.
the usecases with maven porject popup being slow due to open required projects action popup creation are now (8.0) a bit faster. The module project iteration is no longer recursive and only direct child projects are shown. Additionally ww now only show explicit "subprojects" as defined in pom.xml <modules> section. Previously we also used FileOwnerQeury to link to dependency projects.
some reports are duplicate of reports for issue 207155
> the usecases with maven porject popup being slow due to open required projects action popup creation are now (8.0) a bit faster... hm, no reports since 8.0 and over a year ago. Closing ...