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 - OutOfMemoryError: GC overhead limit exceeded
Summary: OutOfMemoryError: GC overhead limit exceeded
Status: NEW
Alias: None
Product: editor
Classification: Unclassified
Component: Parsing & Indexing (show other bugs)
Version: 8.1
Hardware: All All
: P3 normal (vote)
Assignee: Tomas Zezula
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-11-30 20:20 UTC by ytn01
Modified: 2015-11-30 20:20 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter: 221420

Attachments
stacktrace (2.39 KB, text/plain)
2015-11-30 20:20 UTC, ytn01 		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 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