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 254966 - OutOfMemoryError: GC overhead limit exceeded
Summary: OutOfMemoryError: GC overhead limit exceeded
Status: RESOLVED DUPLICATE of bug 230493
Alias: None
Product: platform
Classification: Unclassified
Component: Output Window (show other bugs)
Version: 8.0
Hardware: All All
: P3 normal (vote)
Assignee: Jaroslav Havlin
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-09-03 11:42 UTC by doctordog
Modified: 2015-09-04 11:52 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter: 204747


Attachments
stacktrace (1.79 KB, text/plain)
2015-09-03 11:42 UTC, doctordog
Details

Note You need to log in before you can comment on or make changes to this bug.
Description doctordog 2015-09-03 11:42:46 UTC
Build: NetBeans IDE 8.0.2 (Build 201411181905)
VM: Java HotSpot(TM) 64-Bit Server VM, 25.60-b23, Java(TM) SE Runtime Environment, 1.8.0_60-b27
OS: Mac OS X

User Comments:
GUEST: Was unresponsive after leaving it overnight.

GUEST: 1. ?????? "????????? ?????"
2. ?????? ?????????? ??????????
3. ????????? ????????? ????????

GUEST: I think I was uploading a lot of files. Not really sure. Like after performing "npm install" or something.

GUEST: Run J2EE project.

GUEST: Try to var_dump a big object.

GUEST: ???????

doctordog: After BIG updates on my remote server - NetBeans starts to work so slow. And then I use 'kill ' on my Mac Os to remove this proccess.

GUEST: Left minimized overnight

GUEST: git was uploading git reset --hard to remote server

GUEST: running a java app for more than 8 hours

GUEST: downloading a project from remote ftp

GUEST: <Please provide a description of the problem or the steps to reproduce>
When a webproject with infinite loop is deployed in glassfish debug mode and the debug is terminated the webproject continues to run on the server in an infinite loop that can not end and the process of netbeans has to be killed in order for everything to work properly again.

GUEST: Optimizing NN using GA for 770+ minutes...

GUEST: During normal editing of a Java file Netbeans just stopped responding.

GUEST: It was using almost all of my memory and I couldn't login




Stacktrace: 
java.lang.OutOfMemoryError: GC overhead limit exceeded
   at org.netbeans.core.output2.OutputDocument$DO.getChildrenAdded(OutputDocument.java:796)
   at org.netbeans.core.output2.ExtPlainView.updateDamage(ExtPlainView.java:346)
   at javax.swing.text.PlainView.changedUpdate(PlainView.java:477)
   at javax.swing.plaf.basic.BasicTextUI$RootView.changedUpdate(BasicTextUI.java:1638)
   at javax.swing.plaf.basic.BasicTextUI$UpdateHandler.changedUpdate(BasicTextUI.java:1899)
   at org.netbeans.core.output2.OutputDocument.fireDocumentEvent(OutputDocument.java:529)
Comment 1 doctordog 2015-09-03 11:42:49 UTC
Created attachment 155855 [details]
stacktrace
Comment 2 Jaroslav Havlin 2015-09-04 11:52:18 UTC
> doctordog: After BIG updates on my remote server - NetBeans starts to work so 
> slow. And then I use 'kill ' on my Mac Os to remove this proccess.
The heap dump contains an AquaTabbedPaneContrastUI with a lot of htmlViews.

This is a duplicate of bug 230493.

Thank you for reporting.

*** This bug has been marked as a duplicate of bug 230493 ***