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.
Product Version = NetBeans IDE 8.0.2 (Build 201411181905) Operating System = Mac OS X version 10.10.4 running on x86_64 Java; VM; Vendor = 1.8.0_45 Runtime = Java HotSpot(TM) 64-Bit Server VM 25.45-b02 I think this may apply only to Maven projects. When a java program is run from the IDE two processes are spawned "org.codehaus.plexus.classworlds.launcher.Launcher" and the one requested. When the stop button on the output panel is pressed the Launcher is terminated but the program you request to run is not.
maven calls Processes.killTree(prcs, env) please evaluate
Can you try the latest dev build or beta?
HI, I just use the java command line jps -l. To list the running java processes. I've just tested the beta version 8.1 and the issue is still there I'm running a project ProhireGridGainNodeMain. when I execute from Netbeans I get the following listing $ jps -l 13136 org.codehaus.plexus.classworlds.launcher.Launcher 13139 com.prohire.ProhireGridGainNodeMain 13140 sun.tools.jps.Jps 2471 13097 org.netbeans.Main After I press the red square stop button in the output I get this $ jps -l 13139 com.prohire.ProhireGridGainNodeMain 13141 sun.tools.jps.Jps 2471 13097 org.netbeans.Main As you can see the ProhireGridGainNodeMain is still running but the org.codehaus.plexus.classworlds.launcher.Launcher was killed So I run the project multiple times form the IDE I end up with many copies of ProhireGridGainNodeMain process running in the background even when I push the stop button. Ken
*** Bug 232322 has been marked as a duplicate of this bug. ***
*** Bug 254930 has been marked as a duplicate of this bug. ***
It was interesting to see that the bug 232322 was marked as a duplicate of this and not the other way. That bug is way older than this one. It was reported in 2013 and has been unresolved for over two years now. For people who want to do Maven based Spring applications, this will be a show stopper and hence people will not leave Eclipse or other IDEs that do not show this behaviour. I recommend that the priority on the bug be raised and it be fixed in the next possible release.