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 8.0 (Build 201403101706) VM: Java HotSpot(TM) 64-Bit Server VM, 24.51-b03, Java(TM) SE Runtime Environment, 1.7.0_51-b13 OS: Windows 7 User Comments: Xian_404: I have 8GB of RAM, looks like NBs had gobbled up all available, 7.6GBs, and became unresponsive. Maybe a memory leak? FYI, love the app, you guys are doing a great job! Stacktrace: java.lang.OutOfMemoryError: GC overhead limit exceeded at java.security.AccessControlContext.optimize(AccessControlContext.java:440) at java.security.ProtectionDomain$1.doIntersectionPrivilege(ProtectionDomain.java:76) at java.awt.EventQueue.dispatchEvent(EventQueue.java:703) at org.netbeans.core.TimableEventQueue.dispatchEvent(TimableEventQueue.java:159) at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:242) at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:161)
Created attachment 146635 [details] stacktrace
There is 210,545 instances of sun.awt.EventQueueItem. Most o them has org.netbeans.modules.editor.lib2.view.DocumentViewOp$3 as runnable task. It looks like AWT event queue has over 200,000 items, which is quite strange. Another strange thing is that RequestProcessor queue size is 3336. The tasks in RequestProcessor queue are org.netbeans.spi.editor.hints.HintsController$1, which holds ErrorDescriptions instances and ErrorWrappers instances. Reassigning to editor to investigate, why AWT event queue and RequestProcessor queue are so long.
Unfortunately there is no heapdump from report 720521 for which Tomas commented on this bug. The other report 756985 is duplicate of 230493 since AquaTabbedPaneContrastUI has a huge size. THis seems of bug of jdk 1.7 on mac. I would update it. *** This bug has been marked as a duplicate of bug 230493 ***