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 7.4 (Build 201310111528) VM: Java HotSpot(TM) Client VM, 24.45-b08, Java(TM) SE Runtime Environment, 1.7.0_45-b18 OS: Linux User Comments: vgrigory: just opened IDE GUEST: . Stacktrace: java.lang.OutOfMemoryError: Java heap space at java.lang.Throwable.getStackTraceElement(Throwable.java:0) at java.lang.Throwable.getOurStackTrace(Throwable.java:827) at java.lang.Throwable.getStackTrace(Throwable.java:816) at org.netbeans.modules.masterfs.filebasedfs.utils.FileChangedManager.isClassLoading(FileChangedManager.java:322) at org.netbeans.modules.masterfs.filebasedfs.utils.FileChangedManager.waitIOLoadLowerThan(FileChangedManager.java:218) at org.netbeans.modules.masterfs.filebasedfs.utils.FileChangedManager.pingIO(FileChangedManager.java:255)
Created attachment 142990 [details] stacktrace
The biggest instance is org.netbeans.modules.parsing.lucene.LuceneIndex
(In reply to Jaroslav Havlin from comment #2) > The biggest instance is org.netbeans.modules.parsing.lucene.LuceneIndex I'm sorry for the partial comment, it was corrupted during login. The biggest instance is org.netbeans.modules.parsing.lucene.LuceneIndex#63 (191 MB). I'm not sure whether this is a bug, or there is just not enough memory for opened projects. Reassigning to editor/Parsing & Indexing. Please evaluate it. Vgrigory, please try setting the Xmx parameter, see https://performance.netbeans.org/howto/jvmswitches/.
*** This bug has been marked as a duplicate of bug 239570 ***