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.

Bug 185230 - OutOfMemoryError in nexus indexer
Summary: OutOfMemoryError in nexus indexer
Status: RESOLVED DUPLICATE of bug 185080
Alias: None
Product: projects
Classification: Unclassified
Component: Maven (show other bugs)
Version: 6.x
Hardware: All All
: P3 normal (vote)
Assignee: David Simonek
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-04-29 08:31 UTC by talofo
Modified: 2010-07-29 14:06 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter: 165617


Attachments
stacktrace (3.00 KB, text/plain)
2010-04-29 08:31 UTC, talofo
Details

Note You need to log in before you can comment on or make changes to this bug.
Description talofo 2010-04-29 08:31:46 UTC
Build: NetBeans IDE Dev (Build 201002152000)
VM: Java HotSpot(TM) 64-Bit Server VM, 16.2-b04-271, Java(TM) SE Runtime Environment, 1.6.0_19-b04-271-10M3050
OS: Mac OS X

User Comments:
GUEST: I'm working with a multi-module Maven project, and have both the root module open as well as a single web application module which is the child of the root.  Source control in use is www.bitbucket.org, therefor Hg.  Web Application is a JSF 2.0/CDI application, and is currently deployed in the provided Glassfish container using the Java DB, both of which are running.

Problem is first detected while working in an index.xhtml page, and attempting to use the CTRL-Space autocomplete on an expression that exists in a named CDI bean, however I don't know for sure that the problem started with this event.  I recently updated to 6.9m1 in order to see if this problem has been fixed -- it obviously has not.

Symptom is that memory shoots through the roof (I have a max of ~1Gb), and CPU remains between 50-60%.  Makes NetBeans unusable while in this state.

As I write this, the problem may have resolved itself -- I see that CPU is back down to normal, around 0-6%

GUEST: "Scanning projects..." I've got Zend Framework included in some of my projects with  a lot of files. Maybe that's why the scanning projects take so long time and eats all of my memory.

GUEST: Scanning projects.

talofo: netbeans 6.9 - while scanning after start up. Always running 196 of 197 and sometimes 197 of 197 mb - after this - he runs 117mb of 197mb on idle witch, I believe, it's still to much - and, for apparently no reason he keeps augmenting and augmenting and it's now on 160mb... And still on idle.




Stacktrace: 
java.lang.OutOfMemoryError: Java heap space
   at java.util.Arrays.copyOf(Arrays.java:2882)
   at java.lang.AbstractStringBuilder.expandCapacity(AbstractStringBuilder.java:100)
   at java.lang.AbstractStringBuilder.append(AbstractStringBuilder.java:572)
   at java.lang.StringBuilder.append(StringBuilder.java:203)
   at java.io.UnixFileSystem.resolve(UnixFileSystem.java:93)
   at java.io.File.<init>(File.java:207)
Comment 1 talofo 2010-04-29 08:31:51 UTC
Created attachment 98256 [details]
stacktrace
Comment 2 Jaroslav Tulach 2010-04-29 14:38:02 UTC
We know the maven indexer is too memory hungry, don't we? Tondo?

http://statistics.netbeans.org/exceptions/exception.do?id=359867
Comment 3 Antonin Nebuzelsky 2010-07-29 14:06:35 UTC
Fixed in 6.9 as issue 185080.

*** This bug has been marked as a duplicate of bug 185080 ***