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 8.1 (Build 201510222201) VM: Java HotSpot(TM) 64-Bit Server VM, 25.40-b25, Java(TM) SE Runtime Environment, 1.8.0_40-b26 OS: Windows 8 User Comments: crinus: I was trying to compile a project. This project is classical Java, which runs on top of Glassfish. Glassfish is configured as a server in Netbeans. I'd really be glad to have any kind of feedback. Working on a project so this is not a hobby for me. (Yeah, I know, who would want to have unstable IDE, but yes, am truly very interested in getting this sorted out! :) I've had the similar kind for as long as I have run Netbeans. Now I am running 8.1 so I thought these wouldn't occur. I've had a few thoughts of my own, this is simply a hunch; one thing is that these GC overhead would be caused by the parsers, who are reading source code. I don't know whether NB places emphasis on which project is currently being "worked on", or do all of the background scanning functions take place for all projects regardless of state ? I got 2 projects mounted, since we're making a client-server single-page web app with a Java server. The "non-Java" part (client) thus contains a lot of source files and Stacktrace: java.lang.OutOfMemoryError: GC overhead limit exceeded at java.lang.SecurityManager.checkPackageAccess(SecurityManager.java:1563) at java.lang.ClassLoader$1.run(ClassLoader.java:502) at java.lang.ClassLoader$1.run(ClassLoader.java:500) at java.security.AccessController.doPrivileged(AccessController.java:0) at java.lang.ClassLoader.checkPackageAccess(ClassLoader.java:500) at org.netbeans.core.TimableEventQueue.createSelfSampler(TimableEventQueue.java:263)
Created attachment 158003 [details] stacktrace