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 244652 - OutOfMemoryError: GC overhead limit exceeded
Summary: OutOfMemoryError: GC overhead limit exceeded
Status: RESOLVED DUPLICATE of bug 239360
Alias: None
Product: platform
Classification: Unclassified
Component: Filesystems (show other bugs)
Version: 8.0
Hardware: All All
: P3 normal (vote)
Assignee: Jaroslav Havlin
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-05-22 08:13 UTC by ShivarajRH
Modified: 2014-05-23 08:48 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter: 202792


Attachments
stacktrace (1.41 KB, text/plain)
2014-05-22 08:13 UTC, ShivarajRH
Details

Note You need to log in before you can comment on or make changes to this bug.
Description ShivarajRH 2014-05-22 08:13:29 UTC
Build: NetBeans IDE 8.0 (Build 201403101706)
VM: Java HotSpot(TM) 64-Bit Server VM, 24.45-b08, Java(TM) SE Runtime Environment, 1.7.0_45-b18
OS: Windows 7

User Comments:
ShivarajRH: Editor Hanged for Half an Hour while working.

GUEST: <Please provide a description of the problem or the steps to reproduce>...




Stacktrace: 
java.lang.OutOfMemoryError: GC overhead limit exceeded
   at java.util.Arrays.copyOfRange(Arrays.java:2694)
   at java.lang.String.<init>(String.java:203)
   at java.lang.String.toLowerCase(String.java:2501)
   at java.io.Win32FileSystem.hashCode(Win32FileSystem.java:598)
   at java.io.File.hashCode(File.java:2102)
   at org.netbeans.modules.masterfs.filebasedfs.utils.Utils.hashCode(Utils.java:93)
Comment 1 ShivarajRH 2014-05-22 08:13:32 UTC
Created attachment 147387 [details]
stacktrace
Comment 2 Jaroslav Havlin 2014-05-23 08:48:29 UTC
Report 725674:
 1.5M instances of org.netbeans.lib.lexer.token.DefaultToken
 900k instances of org.netbeans.modules.editor.lib2.highlighting.HighlightItem
 Retained size of all instances of o.n.m.editor.lib2.view.ParagraphView is 267 MB

Probably duplicate of bug 239360.

Thank you for reporting.

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