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 144298 - [65cat] OutOfMemoryError: GC overhead limit exceeded
Summary: [65cat] OutOfMemoryError: GC overhead limit exceeded
Status: CLOSED DUPLICATE of bug 143234
Alias: None
Product: ide
Classification: Unclassified
Component: Performance (show other bugs)
Version: 3.x
Hardware: All All
: P3 blocker (vote)
Assignee: Jiri Skrivanek
URL: http://statistics.netbeans.org/except...
Keywords:
Depends on:
Blocks:
 
Reported: 2008-08-18 18:50 UTC by Unknown
Modified: 2011-05-25 11:38 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter: 93656


Attachments
stacktrace (55 bytes, text/plain)
2008-08-18 18:50 UTC, Unknown
Details
3 log files in my log directory (38.88 KB, application/octet-stream)
2008-08-19 15:04 UTC, Unknown
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Unknown 2008-08-18 18:50:03 UTC
Build: NetBeans IDE Dev (Build 200808170243)
VM: Java HotSpot(TM) 64-Bit Server VM, 10.0-b23, Java(TM) SE Runtime Environment, 1.6.0_07-b06
OS: Linux, 2.6.26-1.slh.3-sidux-amd64, amd64

User Comments: 


Stacktrace: 
java.lang.OutOfMemoryError: GC overhead limit exceeded
        at org.openide.filesystems.FileUtil.getArchiveFile(FileUtil.java:1603)
        at org.netbeans.modules.java.j2seplatform.libraries.JavadocForBinaryQueryLibraryImpl.isNormalizedURL(JavadocForBinaryQueryLibraryImpl.java:175)
        at org.netbeans.modules.java.j2seplatform.libraries.JavadocForBinaryQueryLibraryImpl.getNormalizedURL(JavadocForBinaryQueryLibraryImpl.java:146)
        at org.netbeans.modules.java.j2seplatform.libraries.JavadocForBinaryQueryLibraryImpl.findJavadoc(JavadocForBinaryQueryLibraryImpl.java:131)
        at org.netbeans.api.java.queries.JavadocForBinaryQuery.findJavadoc(JavadocForBinaryQuery.java:85)
        at org.netbeans.modules.javadoc.search.JavadocRegistry.readRoots(JavadocRegistry.java:172)
Comment 1 Unknown 2008-08-18 18:50:10 UTC
Created attachment 67728 [details]
stacktrace
Comment 2 Jiri Skrivanek 2008-08-19 08:15:53 UTC
Is there a way how to reproduce it?
Comment 3 Unknown 2008-08-19 14:25:25 UTC
Not readily.  This was an automated submission.  I use the latest build 100% during my workday.  I restart NB 1 maybe
twice during the day (depending on Java Reult = -1 which I get).  

BTW... what version of the IDE are you guys using to build the IDE?
Comment 4 Jiri Skrivanek 2008-08-19 14:39:15 UTC
It might be a problem with memory settings. Could you attach your messages.log?
Comment 5 Unknown 2008-08-19 15:04:48 UTC
Created attachment 67813 [details]
3 log files in my log directory
Comment 6 Jiri Skrivanek 2008-08-19 15:35:57 UTC
So, try to increase heap size. Go to netbeans/etc/netbeans.conf (or modify command-line) and add something like this

-J-Xmx1024m

Or you can try to enable Concurrent Mark & Sweep garbage collector as described in netbeans.conf. Or use option to
disable "GC overhead limit exceeded" errors http://java.sun.com/javase/technologies/hotspot/gc/gc_tuning_6.html#par_gc.oom.
Comment 7 Unknown 2008-08-19 15:51:36 UTC
I will... But here's the thing (I think I mentioned it either in a defect or on the CAT)
I think the installer ought to intelligently write the netbeans.conf file.  It knows the system it's installing on.
In other words, it knows I'm not installing on a Mac, so it doesn't need the menu bar designation, and it knows I'm
using 64 bit java.  It should fill in appropriate default values.  It can't really be a one size fits all (until the jvm
self-configures)
Comment 8 Jiri Skrivanek 2008-08-20 08:57:48 UTC
Xmx size is calculated from system parameters before IDE starts. I am reassigning to launcher maintainer to evaluate
whether calculated size is corresponding to your system.
Comment 9 t_h 2008-08-20 10:16:16 UTC
According to attached log file Xmx size was set to 512MB which should be enough. If you ran out memory it was probably
due to memory leaks. You can try to attach heap dump to help investigate...reassigning back, there is nothing it can be
done in launcher
Comment 10 Unknown 2008-08-20 12:46:56 UTC
How do I get a heap dump?
Comment 11 Tomas Pavek 2008-08-25 18:05:52 UTC
Maybe duplicate of issue 143234? Looks very similar, 143234 is just shows slowness near the heap limit.
Comment 12 Jiri Skrivanek 2008-09-03 10:51:42 UTC

*** This issue has been marked as a duplicate of 143234 ***