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 250695 - OutOfMemoryError: Java heap space
Summary: OutOfMemoryError: Java heap space
Status: RESOLVED WORKSFORME
Alias: None
Product: guibuilder
Classification: Unclassified
Component: Code (show other bugs)
Version: 8.0
Hardware: All All
: P3 normal (vote)
Assignee: issues@guibuilder
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-02-25 15:07 UTC by Exceptions Reporter
Modified: 2015-09-10 16:52 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter: 215669


Attachments
stacktrace (2.34 KB, text/plain)
2015-02-25 15:07 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-02-25 15:07:13 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, 25.0-b70, Java(TM) SE Runtime Environment, 1.8.0-b132
OS: Windows 7

User Comments:
GUEST: Project design is not loading




Stacktrace: 
java.lang.OutOfMemoryError: Java heap space
   at java.awt.image.DataBufferInt.<init>(DataBufferInt.java:75)
   at java.awt.image.Raster.createPackedRaster(Raster.java:467)
   at java.awt.image.DirectColorModel.createCompatibleWritableRaster(DirectColorModel.java:1032)
   at java.awt.image.BufferedImage.<init>(BufferedImage.java:340)
   at com.sun.java.swing.plaf.windows.XPStyle$SkinPainter.createImage(XPStyle.java:673)
   at sun.swing.CachedPainter.paint0(CachedPainter.java:139)
Comment 1 Exceptions Reporter 2015-02-25 15:07:14 UTC
Created attachment 152214 [details]
stacktrace
Comment 2 Tomas Hurka 2015-02-25 15:09:51 UTC
Large image created by form editor. See "AWT-EventQueue-0" stack trace and java.awt.image.DataBufferInt#241
Comment 3 Tomas Pavek 2015-09-10 16:52:57 UTC
I don't see a large image by GUI builder here. Seems like painting a border of a tabbed pane run out of memory. The form was likely extremely large. It might be similar to bug 243937, though I was not able to reproduce it. There's not much we can do here, since 8.1 the OOME from painting get caught at least.