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: | Unpacking index for OSS Sonatype Staging consuming 8Gb of RAM | ||
---|---|---|---|
Product: | projects | Reporter: | thundernet <thundernet> |
Component: | Maven | Assignee: | Tomas Stupka <tstupka> |
Status: | NEW --- | ||
Severity: | normal | CC: | FiruzzZ |
Priority: | P3 | ||
Version: | 8.2 | ||
Hardware: | PC | ||
OS: | Windows 7 x64 | ||
Issue Type: | DEFECT | Exception Reporter: | |
Bug Depends on: | 253322 | ||
Bug Blocks: |
Description
thundernet
2017-02-10 14:26:15 UTC
I've come across the same issue in 8.0.2 and 8.2 (not tried 8.1 or other intermediate releases). I'm running on Windows 7. Several Maven based war projects. I can post effective POMs if need be although I'm not sure they'll be terribly useful. I think a clean and build tries to load the sonatype-oss-public repository index. This takes an awfully long time to start with. However, when the status bar shows 'Unpacking index for sonatype-oss-public' memory usage jumps up and up until it's using over 6GB and I have to kill the Netbeans64.exe process (I've got 8GB). This will usually take place over a period of a few hours. I've added -J-Dmaven.indexing.doNotAutoIndex=sonatype-oss-public in netbeans.conf (on the 8.2 release) and memory usage seems stable at just over 2GB although I'll be keeping an eye on it. Usage is creeping up but that could just be normal caching. I think this is definitely a live issue and warrants a bit more investigation. Perhaps index unpacking for certain repo's should be switched off by default? It does pretty much make netbeans useless when it's happening. I considered switching IDEs. Any attempt to auto complete in, for example, a spring definition XML seems to set off whatever process is consuming all the memory. I'm having to restart my IDE several times a day. |