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 257044 - OutOfMemoryError: GC overhead limit exceeded
Summary: OutOfMemoryError: GC overhead limit exceeded
Status: NEW
Alias: None
Product: platform
Classification: Unclassified
Component: Filesystems (show other bugs)
Version: 8.1
Hardware: All All
: P3 normal (vote)
Assignee: Jaroslav Havlin
Depends on:
Reported: 2015-12-08 08:25 UTC by pmaselkowski
Modified: 2016-01-05 07:24 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter: 221567

stacktrace (2.66 KB, text/plain)
2015-12-08 08:25 UTC, pmaselkowski

Note You need to log in before you can comment on or make changes to this bug.
Description pmaselkowski 2015-12-08 08:25:40 UTC
Build: NetBeans IDE 8.1 (Build 201510222201)
VM: OpenJDK 64-Bit Server VM, 24.85-b03, OpenJDK Runtime Environment, 1.7.0_85-b01
OS: Linux

User Comments:
pmaselkowski: It hung on checking for external changes.

java.lang.OutOfMemoryError: GC overhead limit exceeded
   at java.lang.StringCoding$StringEncoder.encode(
   at java.lang.StringCoding.encode(
   at java.lang.String.getBytes(
Comment 1 pmaselkowski 2015-12-08 08:25:42 UTC
Created attachment 157712 [details]
Comment 2 Ondrej Vrabec 2015-12-23 17:37:26 UTC
A lot of memory is consumed in Git, that's true. There is even a huge amount of scheduled tasks in a RP in Git. But that's probably because Git is periodically asked about file after file. There is probably a cyclic symlink in the file tree, see the thread "Project prescan initiator". The stacktrace is suspiciously deep and the file name is strange too: see the path for
Comment 3 pmaselkowski 2016-01-05 07:24:43 UTC
Symlinks might be problem, as I use a lot of them in projects, and it is possible that they cycle.

It does not happen always. Will try to observe when it is happening.