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 257555

Summary:	OutOfMemoryError: GC overhead limit exceeded
Product:	cnd	Reporter:	Exceptions Reporter <exceptions_reporter>
Component:	Remote	Assignee:	Vladimir Kvashin <vkvashin>
Status:	RESOLVED DUPLICATE
Severity:	normal
Priority:	P3
Version:	8.0
Hardware:	All
OS:	All
Issue Type:	DEFECT	Exception Reporter:	222101
Attachments:	stacktrace

Description Exceptions Reporter 2016-01-13 22:42:56 UTC

Build: NetBeans IDE 8.0.2 (Build 201411181905)
VM: Java HotSpot(TM) 64-Bit Server VM, 25.11-b03, Java(TM) SE Runtime Environment, 1.8.0_11-b12
OS: Linux

User Comments:
GUEST: no specific causes




Stacktrace: 
java.lang.OutOfMemoryError: GC overhead limit exceeded
   at java.util.Arrays.copyOf(Arrays.java:3326)
   at java.lang.AbstractStringBuilder.expandCapacity(AbstractStringBuilder.java:137)
   at java.lang.AbstractStringBuilder.ensureCapacityInternal(AbstractStringBuilder.java:121)
   at java.lang.AbstractStringBuilder.append(AbstractStringBuilder.java:622)
   at java.lang.StringBuilder.append(StringBuilder.java:202)
   at org.netbeans.modules.remote.impl.fs.RemoteLinkBase.wrapFileObject(RemoteLinkBase.java:110)

Comment 1 Exceptions Reporter 2016-01-13 22:42:58 UTC

Created attachment 158121 [details]
stacktrace

Comment 2 Alexander Simon 2016-01-14 08:38:24 UTC

142,073,264 bytes in 433,656 instances of the class
org.netbeans.modules.remote.impl.fs.RemoteLinkChild

It looks like remote FS does not have protection on "infinite" loop in case
recursive link like to "/usr/bin/X11/X11/X11/X11/X11/...."

Comment 3 Vladimir Kvashin 2016-03-17 13:05:37 UTC

Yes, the reason is cyclic links. Heap dump shows 4062 remote plain files, 370 remote directories, 243 remote links and and 433656 instances of RemoteLinkChild! You can only achieve this via cyclic links.

So the root cause is quite the same as in issue 258298, which has been already fixed.

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