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 258663 - OutOfMemoryError: Java heap space
Summary: OutOfMemoryError: Java heap space
Status: RESOLVED FIXED
Alias: None
Product: ide
Classification: Unclassified
Component: Performance (show other bugs)
Version: 8.0
Hardware: All All
: P3 normal (vote)
Assignee: Tomas Hurka
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-04-05 14:47 UTC by greenfrog
Modified: 2016-04-21 16:06 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter: 215100


Attachments
stacktrace (1.46 KB, text/plain)
2016-04-05 14:47 UTC, greenfrog
Details

Note You need to log in before you can comment on or make changes to this bug.
Description greenfrog 2016-04-05 14:47:45 UTC
Build: NetBeans IDE 8.0.2 (Build 201411181905)
VM: Java HotSpot(TM) Client VM, 25.40-b25, Java(TM) SE Runtime Environment, 1.8.0_40-b26
OS: Linux

User Comments:
greenfrog: Nothing special. Just had the program open for a while, with 6 files open. Netbeans memory usage just keeps growing and growing for no discernable reason, making it run very slowly.

GUEST: Nothing? Went to different window, came back and it would never come back up.

GUEST: Please provide a description of the problem or the steps to reproduce

GUEST: Hi Netbenas is not working proeprly .....................




Stacktrace: 
java.lang.OutOfMemoryError: Java heap space
   at java.util.Arrays.copyOfRange(Arrays.java:3664)
   at java.lang.String.<init>(String.java:201)
   at java.lang.String.substring(String.java:1957)
   at java.awt.datatransfer.MimeTypeParameterList.parse(MimeTypeParameterList.java:143)
   at java.awt.datatransfer.MimeTypeParameterList.<init>(MimeTypeParameterList.java:56)
   at java.awt.datatransfer.MimeType.parse(MimeType.java:174)
Comment 1 greenfrog 2016-04-05 14:47:46 UTC
Created attachment 159122 [details]
stacktrace
Comment 2 Tomas Hurka 2016-04-21 16:06:59 UTC
Please try NetBeans 8.1. If you are still able to reproduce it, please file a
new bug. Thanks.