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.0.2 (Build 201411181905) VM: Java HotSpot(TM) 64-Bit Server VM, 24.76-b04, Java(TM) SE Runtime Environment, 1.7.0_76-b13 OS: Linux User Comments: pdeville: deploy a war on apache tomee GUEST: Project Compiles and Clean and Builds correct. After Run this message comes: java.lang.OutofMemoryError: unable to create native thread at java.lang.thread.start0(Native Method) at java.lang.Threat.start(Thread.java: 597 ) at org.apache.... GUEST: El debug se ejecuta solo, y no me deja editar las clases. Cada vez que intento editarla se ejecuta el debug. Stacktrace: java.lang.OutOfMemoryError: unable to create new native thread at java.lang.Thread.start0(Thread.java:0) at java.lang.Thread.start(Thread.java:714) at com.sun.tools.jdi.TargetVM.start(TargetVM.java:62) at com.sun.tools.jdi.VirtualMachineImpl.<init>(VirtualMachineImpl.java:190) at com.sun.tools.jdi.VirtualMachineManagerImpl.createVirtualMachine(VirtualMachineManagerImpl.java:231) at com.sun.tools.jdi.VirtualMachineManagerImpl.createVirtualMachine(VirtualMachineManagerImpl.java:241)
Created attachment 151941 [details] stacktrace
This issue should be looked at before 8.1.
There is no heap dump, because this OOME was not caused by a lack of heap space, but by too many created threads. The two newest reports have both a large number of exceptions and messages in their logs. But we do not have a thread dump, which would indicate if there are some leaking threads. The 7.4 report has many warnings like: "WARNING: Unable to submit line breakpoint to file:/XXX at line XXX, reason: No source root found for URL 'file:/XXX'. Verify the setup of project sources." These come from debugger and looks like generated in a loop. It also contains: SEVERE java.lang.NullPointerException at org.netbeans.modules.debugger.jpda.projects.RunToCursorActionProvider.debugProject(RunToCursorActionProvider.java:154) at org.netbeans.modules.debugger.jpda.projects.RunToCursorActionProvider.invokeAction(RunToCursorActionProvider.java:150) at org.netbeans.modules.debugger.jpda.projects.RunToCursorActionProvider.access$300(RunToCursorActionProvider.java:76) at org.netbeans.modules.debugger.jpda.projects.RunToCursorActionProvider$1$1.run(RunToCursorActionProvider.java:135) at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:241) ... There are multiple OOMEs comming via RunToCursorActionProvider.debugProject(), which indicates that there were many attempts to start debugger via Run To Cursor action. If the debugger was started in a large amount of attempts, a large number of threads could be created, because every start of debugger starts some threads in NetBeans JVM. The 8.0.2 report has many warnings like: WARNING [org.openide.util.WeakListenerImpl]: Can't remove org.netbeans.api.java.source.ClassIndexListener using method org.netbeans.api.java.source.ClasspathInfo.removeClassIndexListener from ClasspathInfo
Reproduced by holding F4 down. A large number of debugging sessions is started.
Fixed by changeset: 288660:bcf0743555fb http://hg.netbeans.org/core-main/rev/bcf0743555fb
Integrated into 'main-silver', will be available in build *201506070001* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main-silver/rev/bcf0743555fb User: mentlicher@netbeans.org Log: #250357: Prevent from proliferation of debugger sessions on Run To Cursor action.