Question
Air application not closing correctly
Hello,
I'm working on an AIR project for a client and I'm having a problem: some testers reported that after closing the application they can still see the application running in the task manager using about 50% of the cpu.
From what we where able to see, this problem is present only in Windows XP SP2. If the same application is run on XP SP3 or Mac the application exits as expected.
If the application is opened again, a new instance of the application is visible in the task manager. After closing it both the instances remain in the task manager.
We noticed also that this behavior happens only after the application starts loading data from a web server using a URLLoader. (so far the problem was reported if the application was closed after the request but before the reply of the server, but we are still looking into this)
We tried calling the Close method of the URLLoader before shutting down the application or calling explicitly the NativeApplication.nativeApplication.exit(), but this doesn't affect the outcome.
Can someone suggest a way for us to troubleshoot this?
Thank you very much
Andrea
I'm working on an AIR project for a client and I'm having a problem: some testers reported that after closing the application they can still see the application running in the task manager using about 50% of the cpu.
From what we where able to see, this problem is present only in Windows XP SP2. If the same application is run on XP SP3 or Mac the application exits as expected.
If the application is opened again, a new instance of the application is visible in the task manager. After closing it both the instances remain in the task manager.
We noticed also that this behavior happens only after the application starts loading data from a web server using a URLLoader. (so far the problem was reported if the application was closed after the request but before the reply of the server, but we are still looking into this)
We tried calling the Close method of the URLLoader before shutting down the application or calling explicitly the NativeApplication.nativeApplication.exit(), but this doesn't affect the outcome.
Can someone suggest a way for us to troubleshoot this?
Thank you very much
Andrea
