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 256876

Summary:	OutOfMemoryError: GC overhead limit exceeded
Product:	editor	Reporter:	ytn01
Component:	Parsing & Indexing	Assignee:	Tomas Zezula <tzezula>
Status:	NEW ---
Severity:	normal
Priority:	P3
Version:	8.1
Hardware:	All
OS:	All
Issue Type:	DEFECT	Exception Reporter:	221420
Attachments:	stacktrace

Description ytn01 2015-11-30 20:20:48 UTC

Build: NetBeans IDE 8.1 (Build 201510222201)
VM: Java HotSpot(TM) 64-Bit Server VM, 25.72-b05, Java(TM) SE Runtime Environment, 1.8.0_72-ea-b05
OS: Windows 7

User Comments:
ytn01: I had 3 projects opened:
-a Maven Java project
-a web application (huge project)
-a Gradle application

I left the IDE idle, for around 4 days straight in which I didn't use my computer at all (it was running this whole time).
Coming back to NetBeans, performance was very sluggish and eventually "GC limit exceeded" error wash shown.




Stacktrace: 
java.lang.OutOfMemoryError: GC overhead limit exceeded
   at java.lang.AbstractStringBuilder.<init>(AbstractStringBuilder.java:68)
   at java.lang.StringBuffer.<init>(StringBuffer.java:128)
   at java.net.URI.decode(URI.java:2775)
   at java.net.URI.getPath(URI.java:1311)
   at sun.nio.fs.WindowsUriSupport.fromUri(WindowsUriSupport.java:130)
   at sun.nio.fs.WindowsFileSystemProvider.getPath(WindowsFileSystemProvider.java:92)

Comment 1 ytn01 2015-11-30 20:20:50 UTC

Created attachment 157565 [details]
stacktrace