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.
Build: NetBeans IDE Dev (Build 201305252300) VM: Java HotSpot(TM) 64-Bit Server VM, 23.6-b04, Java(TM) SE Runtime Environment, 1.7.0_11-b21 OS: Mac OS X User Comments: nikolaj_a: Generated a LOT of logging lines from the attached GlassFish 4 caused NetBeans to become unresponsive, run low on memory, and eventuelly run completely out of memory. Stacktrace: java.lang.OutOfMemoryError: Java heap space at java.awt.image.DataBufferInt.<init>(DataBufferInt.java:75) at java.awt.image.Raster.createPackedRaster(Raster.java:470) at java.awt.image.DirectColorModel.createCompatibleWritableRaster(DirectColorModel.java:1032) at java.awt.image.BufferedImage.<init>(BufferedImage.java:357) at com.apple.laf.AquaPainter$AquaSingleImagePainter.paintFromSingleCachedImage(AquaPainter.java:151) at com.apple.laf.AquaPainter$AquaSingleImagePainter.paint(AquaPainter.java:136)
Created attachment 135107 [details] stacktrace
You've got -XX:MaxPermSize=384m in your netbeans.conf, try removing that option and reopen if still reproducible.
(In reply to comment #2) > You've got -XX:MaxPermSize=384m in your netbeans.conf, try removing that option > and reopen if still reproducible. I'm running with the completely fresh NetBeans Dev download - no changes in netbeans.conf. There is no MaxPermSize specified, which probably means the OS default. Even if I specify a higher memory allowance, wouldn't it just postpone the problem? When I mention a lot of logging output, I mean a LOT! Millions of logging entries. It seems that there is no limiting measures taken in the netBeans output window whatsoever.
You'll need to adjust the logging level in GlassFish then. Reassigning to Output component for evaluation. Is there any way to limit the number of lines in Output window?
(In reply to comment #4) > You'll need to adjust the logging level in GlassFish then. > Reassigning to Output component for evaluation. Is there any way to limit the > number of lines in Output window? Adjusting the logging level is a good solution, even though in my case everything is actually logged at WARNING level. How about some sort of "rotation", possibly with a textual reference to the real log files if applicable, or just a hard limit to how many output lines are saved in memory? Just throwing suggestions here :)
Not sure the OOME is directly related to output window. Object with biggest retained size is a AquaTabbedPaneContrastUI (425 MB), that contains field htmlViews with 15762 elements. Object that contains data for the Output Window (LinesImpl) has size only 2.8 MB, so it's probably not involved in the OOME. I don't know exactly what the big object is good for. Nikolaj_a, can you see a TabbedPane that contains a lot of tabs? (Or it could be a memory leak.) Standa, please, any ideas? Thanks.
This is a bug in Aqua L&F implementation in JDK 1.7 - when HTML is being used for JTabbedPane tab titles each update of tab titles creates a new instance of BasicHTML.Renderer class without discarding previous instances for the same tab. See AquaTabbedPaneCopyFromBasicUI.updateHtmlViews(int) - it was copied from BasicTabbedPaneUI but is missing htmlViews.removeElementAt(index) call from line 3528 It could be a serious performance problem in NetBeans as we use HTML for tab titles in Output window.
I'm pretty sure I can make a reproducible test case for this. Basically just deploy a simple WAR to the bundled GlassFish 4 with a servlet that starts an infinite loop repeatedly outputting a single log line with WARNING level.
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=8017284 Closing wontfix on NetBeans side.
*** Bug 239660 has been marked as a duplicate of this bug. ***
*** Bug 242503 has been marked as a duplicate of this bug. ***
*** Bug 243023 has been marked as a duplicate of this bug. ***
*** Bug 245497 has been marked as a duplicate of this bug. ***
*** Bug 250481 has been marked as a duplicate of this bug. ***
*** Bug 252113 has been marked as a duplicate of this bug. ***
*** Bug 243671 has been marked as a duplicate of this bug. ***
*** Bug 254966 has been marked as a duplicate of this bug. ***
*** Bug 254652 has been marked as a duplicate of this bug. ***
*** Bug 242834 has been marked as a duplicate of this bug. ***
*** Bug 255580 has been marked as a duplicate of this bug. ***
*** Bug 256882 has been marked as a duplicate of this bug. ***
*** Bug 262453 has been marked as a duplicate of this bug. ***
*** Bug 267791 has been marked as a duplicate of this bug. ***
*** Bug 271326 has been marked as a duplicate of this bug. ***