Details
-
Bug
-
Status: Open
-
Minor
-
Resolution: Unresolved
-
8.2
-
None
-
Product Version: NetBeans IDE 8.2 (Build 201705191307)
Updates: NetBeans IDE is updated to version NetBeans 8.2 Patch 2
Java: 1.8.0_121; Java HotSpot(TM) 64-Bit Server VM 25.121-b13
Runtime: Java(TM) SE Runtime Environment 1.8.0_121-b13
System: Windows 10 version 10.0 running on amd64; Cp1252; en_US (nb)
User directory: C:\Users\Tobi\AppData\Roaming\NetBeans\8.2
Cache directory: C:\Users\Tobi\AppData\Local\NetBeans\Cache\8.2Product Version: NetBeans IDE 8.2 (Build 201705191307) Updates: NetBeans IDE is updated to version NetBeans 8.2 Patch 2 Java: 1.8.0_121; Java HotSpot(TM) 64-Bit Server VM 25.121-b13 Runtime: Java(TM) SE Runtime Environment 1.8.0_121-b13 System: Windows 10 version 10.0 running on amd64; Cp1252; en_US (nb) User directory: C:\Users\Tobi\AppData\Roaming\NetBeans\8.2 Cache directory: C:\Users\Tobi\AppData\Local\NetBeans\Cache\8.2
Description
Referring to https://netbeans.org/bugzilla/show_bug.cgi?id=253322 , our project uses ivy to fetch libraries. In our development branch https://github.com/SensorsINI/jaer/tree/ivy-bagreader , the index update makes a cache that takes hours to update, grows RAM past 16GB, and has final size >41GB in \AppData\Local\NetBeans\Cache\8.2\mavenindex\oss.sonatype.org
Is this expected behavior? During update, the machine (which has 16GB RAM) becomes unusable as everything starts churning the paging file.
The exact point this occurs is https://github.com/SensorsINI/jaer/tree/d6bcf756ca26ae790b73016a61d7188a7b2c3445 but we have seen it as soon as we starting using ivy for fetching packages.
The attached log file does not seem to contain this indexing operation but it might be helpful.