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 229739 - OutOfMemoryError: GC overhead limit exceeded
Summary: OutOfMemoryError: GC overhead limit exceeded
Status: RESOLVED INCOMPLETE
Alias: None
Product: javascript
Classification: Unclassified
Component: Editor (show other bugs)
Version: 7.2
Hardware: All All
: P3 normal (vote)
Assignee: Petr Pisl
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-05-14 16:02 UTC by dcherk
Modified: 2013-05-15 07:38 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter: 200642

Attachments
stacktrace (2.64 KB, text/plain)
2013-05-14 16:02 UTC, dcherk 		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 dcherk 2013-05-14 16:02:11 UTC 
This issue was reported manually by gorrus.
It already has 1 duplicates 


Build: NetBeans IDE 7.2 (Build 201207171143)
VM: Java HotSpot(TM) 64-Bit Server VM, 19.1-b02, Java(TM) SE Runtime Environment, 1.6.0_24-b07
OS: Windows 7

User Comments:
dcherk: find usages of a JavaScript function




Stacktrace: 
java.lang.OutOfMemoryError: GC overhead limit exceeded
   at org.netbeans.Stamps.produceRelativePath(Stamps.java:929)
   at org.netbeans.Stamps.findRelativePath(Stamps.java:967)
   at org.netbeans.JarClassLoader$JarSource.getIdentifier(JarClassLoader.java:806)
   at org.netbeans.Archive.getData(Archive.java:184)
   at org.netbeans.JarClassLoader$JarSource.doGetResource(JarClassLoader.java:544)
   at org.netbeans.JarClassLoader$Source.getResource(JarClassLoader.java:347)
Comment 1 dcherk 2013-05-14 16:02:13 UTC 
Created attachment 134436 [details]
stacktrace
Comment 2 Petr Pisl 2013-05-15 07:38:01 UTC 
Thank you for the reporting. It would be better have in such case a memory dump. What you can do in the case of out of memory exception is write up here http://wiki.netbeans.org/FaqNetBeansAndOOME . 

Anyway, you are reporting that this happen in NetBeans 7.2, if you can, please try a newer build. I'm closing this issue as incomplete for now, because from the stacktrace I can not recognized almost nothing. Thanks.