Sunday, April 13, 2008

Killing Flash CS3 / AIR Processes and avoiding the "debugger launch failed" message

To kill an AIR application launched for testing from Flash CS3 open the task manager and kill the process idl.exe.

When working within the Flash CS3 development environment, lightweight or utility windows spawned from an AIR application are not killed when the primary AIR application window is exited. In fact, they are not even killed when Flash CS3 is closed.

Further, as long as these lightweight/utility windows are open you will not be able to to test your application. There simply will be no result from pressing ctrl+enter. Launching the debugger will only offer the message, "debugger launch failed!" If any part of the AIR application is still running you simply will not be able to test your application. Hence, you must go to the task manager and kill idl.exe!

3 comments:

David said...

What if the debugger message reads "Debugger server socket already in use. Debug session will terminate."

Anonymous said...

At the end, do you mean adl.exe instead of idl.exe? Killing adl.exe works for me.

Ringo Moss said...

Cheers man,

I was pulling my hair out over this - just a quick note - if you are using the updated CS3 air versioning (apollo+1) the application to kill is now adl.exe

Much love,

Ringo Moss
http://www.thenerv.co.uk

Post a Comment