Memory leak causes AIR runbtime to remain in memory

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Create an AIR application
2. Add this code in a creattion_complete handler (or anywhere else):
var clazz:Class = ClassUtils.forName(this.className);
var type:Type = Type.forClass(clazz); 
3. Close the application
4. Check Windows Task Manager and see that the process 'adl.exe' remains active

What is the expected output? What do you see instead?
adl.exe ought to have been stopped along with the cl,osing of the
application, but it didn't.

What version of the product are you using? On what operating system?
Latest SVN version.

Please provide any additional information below.
I've attached patches that contain the fix for this issue. It turns out
there was a circular reference between the Type and AbstractMember classes.

Original issue reported on code.google.com by ihatelivelyids on 11 May 2009 at 7:44

Attachments:

• leakfixes.patch

[GoogleCodeExporter]

Original comment by christophe.herreman on 12 May 2009 at 8:02

• Changed state: Accepted

[GoogleCodeExporter]

Original comment by christophe.herreman on 12 May 2009 at 8:56

• Changed state: Fixed