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 175991 - OutOfMemoryError: GC overhead limit exceeded
Summary: OutOfMemoryError: GC overhead limit exceeded
Status: CLOSED DUPLICATE of bug 183289
Alias: None
Product: utilities
Classification: Unclassified
Component: Search (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: Victor Vasilyev
URL: http://statistics.netbeans.org/except...
Keywords:
Depends on:
Blocks:
 
Reported: 2009-11-04 08:37 UTC by Marian Mirilovic
Modified: 2010-04-21 12:46 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter: 161455

Attachments
stacktrace (2.13 KB, text/plain)
2009-11-04 08:37 UTC, Marian Mirilovic 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Marian Mirilovic 2009-11-04 08:37:30 UTC 
Build: NetBeans IDE Dev (Build 200911021401)
VM: Java HotSpot(TM) 64-Bit Server VM, 14.2-b01, Java(TM) SE Runtime Environment, 1.6.0_16-b01
OS: Linux, 2.6.28-15-generic, amd64

User Comments:
mmirilovic: I've got it while serching in project



Stacktrace: 
java.lang.OutOfMemoryError: GC overhead limit exceeded
        at sun.nio.ch.Util.releaseTemporaryDirectBuffer(Util.java:67)
        at sun.nio.ch.IOUtil.read(IOUtil.java:212)
        at sun.nio.ch.FileChannelImpl.read(FileChannelImpl.java:144)
        at org.netbeans.modules.search.BufferedCharSequence$Source.read(BufferedCharSequence.java:507)
        at org.netbeans.modules.search.BufferedCharSequence$Source.readNext(BufferedCharSequence.java:551)
        at org.netbeans.modules.search.BufferedCharSequence$Sink.next(BufferedCharSequence.java:599)
Comment 1 Marian Mirilovic 2009-11-04 08:37:35 UTC 
Created attachment 90477 [details]
stacktrace
Comment 2 Alexei Mokeev 2009-11-10 03:37:38 UTC 
Dangerous sign. One report so far, will look closer for the next release.
Comment 3 Victor Vasilyev 2010-03-31 14:53:57 UTC 

*** This bug has been marked as a duplicate of bug 183289 ***
Comment 4 Marian Mirilovic 2010-04-21 12:46:17 UTC 
verified duplicate