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.0 (Build 201104080000) VM: Java HotSpot(TM) Client VM, 19.0-b09, Java(TM) SE Runtime Environment, 1.6.0_23-b05 OS: Windows 7 User Comments: rptmaestro: I right-clicked on a node in the Maven Repository Explorer and the IDE became completely unresponsive for a while. tpistols: building a maven job in another window (outside of IDE) and attempting to open the local repository browser Maximum slowness yet reported was 27660 ms, average is 11868
Created attachment 107950 [details] nps snapshot
Nothing to do with Maven, I think; that just happened to call NbBundle.getMessage. RefreshSlow in masterfs was running - maybe this sucked up all available I/O throughput.
"slow referesh" is called slow, because it does not consume any I/O. Rather look at the snapshot that shows 8 battler warmer threads. A bit too much for a single maven is not it? Or look into messages.log to see exceptions from nexus-maven-repository-index Or a bunch of activity in parsing. Maybe you'd like to stop maven indexing when parsing is running?
(In reply to comment #3) > "slow [refresh]" is called slow, because it does not consume any I/O. Seems to be calling File.listFiles. > the snapshot [...] shows 8 [bottle] warmer threads. A bit too much > for a single maven is not it? This is just part of Maven Indexer. Anyway eight idle daemon threads would not be causing unresponsiveness. > Or look into messages.log to see exceptions from nexus-maven-repository-index Just a repo without an index; probably unrelated. > Maybe you'd like to stop maven indexing when parsing is running? If there were some API to detect that parsing was in progress, and Maven Indexer offered some API to pause, then sure.