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.
92 duplicates so far ... Build: NetBeans IDE Dev (Build 200708300000) VM: Java HotSpot(TM) Client VM, 1.6.0-b105 OS: Linux, 2.6.20-16-generic, i386 User comments: STACKTRACE: (first 10 lines) java.lang.OutOfMemoryError: Java heap space at java.awt.image.DataBufferInt.<init>(DataBufferInt.java:41) at java.awt.image.Raster.createPackedRaster(Raster.java:458) at java.awt.image.DirectColorModel.createCompatibleWritableRaster(DirectColorModel.java:1015) at java.awt.image.BufferedImage.<init>(BufferedImage.java:312) at org.netbeans.modules.uml.ui.products.ad.viewfactory.ETEGraphImageEncoder.write(ETEGraphImageEncoder.java:210) at org.netbeans.modules.uml.ui.swing.drawingarea.ADDrawingAreaControl$SunSaveAsImageDialog.onOK(ADDrawingAreaControl.java:8952) at com.tomsawyer.editor.export.TSESaveAsImageDialog.actionPerformed(TSESaveAsImageDialog.java:625) at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1995) at javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2318) at javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:387)
most seems to be from one issue, not enouth memory for diagram export, will try to find what can be done in 7.0
Can anybody provide any sample project?
Also available physical memory and if modified java memory options.
As a workaround it may be possible either to increase netbeans memory settings or try to export image with smaller resolution, max possible is dependent on available memory for netbeans.
*** Issue 139337 has been marked as a duplicate of this issue. ***
may miss 7.0 target as it may require not standard images handling, also as mentioned above try to increase memory available for netbeans, also scaling down big diagrams may help. If anybody have a problem with small diagram please attach your project and provide you system memory information, also message.log may help. thanks. Also from 92 duplicates there a lot of duplicates for another modules (not uml), it seems exceptions need to be separated.
Created attachment 92592 [details] stacktrace Got this exception after building two very simple maven projects (without any dependencies) at the same time.
Created attachment 140224 [details] stacktrace Profiling java application
I suppose the issue may bacame a collector for ooms and as uml is unmainteined, it may be a problem
Created attachment 144230 [details] stacktrace ?
Created attachment 144231 [details] stacktrace ?
(In reply to williambacchi from comment #11) > Created attachment 144231 [details] > stacktrace > > ? I was debugging a java application. I set a conditional breakpoint. If I remove the conditional breakpoint no error occurs.