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 250620

Summary:	OutOfMemoryError: Java heap space
Product:	javaee	Reporter:	Exceptions Reporter <exceptions_reporter>
Component:	Persistence	Assignee:	Sergey Petrov <sj-nb>
Status:	NEW ---
Severity:	normal	CC:	ad-nb, allisoncTimeless, fractalcoding, leonferdian, Mirimas, thurka
Priority:	P3
Version:	8.0
Hardware:	All
OS:	All
Issue Type:	DEFECT	Exception Reporter:	215598
Attachments:	stacktrace

Description Exceptions Reporter 2015-02-23 08:25:05 UTC

This issue was reported manually by thurka.
It already has 1 duplicates 


Build: NetBeans IDE 8.0.2 (Build 201411181905)
VM: Java HotSpot(TM) Client VM, 24.71-b01, Java(TM) SE Runtime Environment, 1.7.0_71-b14
OS: Windows 7

User Comments:
GUEST: too slow and not responsive




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-23 08:25:07 UTC

Created attachment 152149 [details]
stacktrace

Comment 2 Tomas Hurka 2015-02-23 08:29:12 UTC

The heap dump contains 5,736,000 of org.eclipse.persistence.jpa.jpql.parser.IdentificationVariableDeclaration instances and 5,736,000 of org.eclipse.persistence.jpa.jpql.parser.AbstractExpression$Info instances. It looks like the problem is caused by parsing the following query:

select c from OlayKayit c inner join kasa k on c.kasaId = k.kasaId where terminalSerialNo = :terminalSerialNo

This look identical to issue #239884 and issue #244886, but this report is from NB 8.0.2, where issue #239884 should be fixed. Please evaluate.