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 252812 - OutOfMemoryError: Java heap space
Summary: OutOfMemoryError: Java heap space
Status: RESOLVED DUPLICATE of bug 244697
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: 2015-06-04 15:50 UTC by Exceptions Reporter
Modified: 2015-06-04 15:52 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter: 217740


Attachments
stacktrace (2.26 KB, text/plain)
2015-06-04 15:50 UTC, Exceptions Reporter
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Exceptions Reporter 2015-06-04 15:50:43 UTC
This issue was reported manually by thurka.
It already has 1 duplicates 


Build: NetBeans IDE 8.0 (Build 201403101706)
VM: Java HotSpot(TM) Client VM, 24.51-b03, Java(TM) SE Runtime Environment, 1.7.0_51-b13
OS: Linux

User Comments:
GUEST: Java causes a memory leak an consumes a lots of resource. This causes NetBeans to freez.




Stacktrace: 
java.lang.OutOfMemoryError: Java heap space
   at java.awt.image.DataBufferInt.<init>(DataBufferInt.java:75)
   at com.sun.java.swing.plaf.gtk.GTKEngine.finishPainting(GTKEngine.java:589)
   at com.sun.java.swing.plaf.gtk.GTKEngine.finishPainting(GTKEngine.java:580)
   at com.sun.java.swing.plaf.gtk.GTKPainter.paintViewportBorder(GTKPainter.java:630)
   at javax.swing.plaf.synth.SynthScrollPaneUI$ViewportBorder.paintBorder(SynthScrollPaneUI.java:256)
   at javax.swing.JComponent.paintBorder(JComponent.java:947)
Comment 1 Exceptions Reporter 2015-06-04 15:50:45 UTC
Created attachment 154060 [details]
stacktrace
Comment 2 Tomas Hurka 2015-06-04 15:52:46 UTC
Retained size of 171 instances of org.netbeans.modules.css.lib.nbparser.CssParser is 529,901,414 bytes, which is 67.9% o the heap.

*** This bug has been marked as a duplicate of bug 244697 ***