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

Summary: OutOfMemoryError: GC overhead limit exceeded
Product: java Reporter: Vladimir Kvashin <vkvashin>
Component: CompilerAssignee: Dusan Balek <dbalek>
Status: NEW ---    
Severity: normal    
Priority: P3    
Version: 8.1   
Hardware: All   
OS: All   
Issue Type: DEFECT Exception Reporter: 221588
Attachments: stacktrace

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.

java.lang.OutOfMemoryError: GC overhead limit exceeded
   at java.lang.StringCoding$StringEncoder.encode(
   at java.lang.StringCoding.encode(
   at java.lang.String.getBytes(
Comment 1 Vladimir Kvashin 2015-12-09 07:28:33 UTC
Created attachment 157728 [details]
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 :)