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 257065 - OutOfMemoryError: GC overhead limit exceeded
Summary: OutOfMemoryError: GC overhead limit exceeded
Status: NEW
Alias: None
Product: java
Classification: Unclassified
Component: Compiler (show other bugs)
Version: 8.1
Hardware: All All
: P3 normal (vote)
Assignee: Dusan Balek
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-12-09 07:28 UTC by Vladimir Kvashin
Modified: 2015-12-09 10:47 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter: 221588


Attachments
stacktrace (3.01 KB, text/plain)
2015-12-09 07:28 UTC, Vladimir Kvashin
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Vladimir Kvashin 2015-12-09 07:28:32 UTC
Build: NetBeans IDE 8.1 (Build 20151201-8f8e169a5194)
VM: Java HotSpot(TM) 64-Bit Server VM, 24.71-b01, Java(TM) SE Runtime Environment, 1.7.0_71-b14
OS: Linux

User Comments:
vkvashin: I worked with 10-15 java projects, ran Java Call Graph, by mistake tried to expand some very common method like toString(), understood that this was a mistake, collapsed the node and proceeded working with IDE. The IDE became sluggish, so I decided to restart it.




Stacktrace: 
java.lang.OutOfMemoryError: GC overhead limit exceeded
   at java.lang.StringCoding$StringEncoder.encode(StringCoding.java:300)
   at java.lang.StringCoding.encode(StringCoding.java:344)
   at java.lang.String.getBytes(String.java:916)
   at java.io.FileOutputStream.open(FileOutputStream.java:0)
   at java.io.FileOutputStream.<init>(FileOutputStream.java:221)
   at java.io.FileOutputStream.<init>(FileOutputStream.java:171)
Comment 1 Vladimir Kvashin 2015-12-09 07:28:33 UTC
Created attachment 157728 [details]
stacktrace
Comment 2 Vladimir Kvashin 2015-12-09 10:47:12 UTC
I filed this FYI; if the only reason is the really really huge java call hierarchy, then I'm OK with closing it: although IDE could still react more properly on such stupid requests, I wouldn't expect it as a must :)