If you are windows you could include a command line option for a taskkill [1] if you have any scripts running.
[1] taskkill /F /IM java.exe -Mark -----Original Message----- From: dhwanishah85 [mailto:dhwanisha...@gmail.com] Sent: Thursday, January 07, 2016 7:02 AM To: dev@flex.apache.org Subject: [Non-DoD Source] NativeProcess is not exiting Hi, I am working on Developing an IDE for flex named "Moonshine". In order to make FDB work, I need to start 3 nativeprocesses. FDB itself is java process and thus it starts java.exe in system processes. When I build-debug my small flex application with intentionally changed AIR version number to wrong number and this will make runtime fail and throwing - "error while loading initial content". Thus we catch this error and step by step making nativeprocess exit. But I can not able to make java.exe exit. And this causes issues when i run application again after correcting the version number in app.xml file. In next run of the application i am getting message from fdb that "(fdb) Another Flash debugger is probably running; please close it. Details: 'Unrecognized Windows Sockets error: 0: JVM_Bind'." Please suggest how to make java.exe exit. -- View this message in context: http://apache-flex-development.2333347.n4.nabble.com/NativeProcess-is-not-exiting-tp51079.html Sent from the Apache Flex Development mailing list archive at Nabble.com.
