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 Dev (Build 1) VM: Java HotSpot(TM) 64-Bit Server VM, 25.31-b07, Java(TM) SE Runtime Environment, 1.8.0_31-b13 OS: Windows 8 User Comments: elennaro: editing big node js project causes out of memory when trying to use autocomplete Stacktrace: java.lang.OutOfMemoryError: GC overhead limit exceeded at java.util.ResourceBundle$CacheKey.clone(ResourceBundle.java:657) at java.util.ResourceBundle.findBundle(ResourceBundle.java:1462) at java.util.ResourceBundle.findBundle(ResourceBundle.java:1419) at java.util.ResourceBundle.getBundleImpl(ResourceBundle.java:1361) at java.util.ResourceBundle.getBundle(ResourceBundle.java:890) at sun.util.resources.LocaleData$1.run(LocaleData.java:164)
Created attachment 153898 [details] stacktrace
org.apache.lucene.document.Field 21.668225523039045 3,672,169 (21.7%) 253,379,661 (24.8%) Also java.util.ArrayDeque#348 in org.netbeans.modules.parsing.lucene.DocumentIndexImpl.query contains over 1 million entries. Not sure if this is JavaScript editor or Parsing API's fault. Maybe JavaScript because it asks for too many entries in code completion?
The report doesn't contain unfortunately the build number. From which days is this build. I have fixed today similar OOM, so it can be fixed, but to be sure, I need to know, from which sources it was build (date). Please reopen, if you can provide this.