[FLEX-17314] [Flash Player] Memory Leak in Button click event.

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: Adobe Flex SDK 3.2 (Release)
• Component/s: mx: Window
• Environment: Affected OS(s): Windows; Affected OS(s): Windows XP; Language Found: English
• Assignee: Adobe JIRA
• Reporter: Adobe JIRA
• Created: 27/Jan/09 15:13
• Updated: 05/Mar/10 19:17
• Resolved: 01/Mar/10 13:30

Description

Steps to reproduce:
1. Create AIR Application that opens a secondary mx:Window.
2. Add an mx:Button to the secondary window whose click handler closes the window.
3 Profile application. Open secondary window a number of times and close window via mx:Button from step 2.

Actual Results:

One instance of the secondary Window and its children remain in memory after closing.

Expected Results:

No instances of the secondary Window nor its children should remain in memory after the Window is closed.

Note:

This is not reproducible with mx:Label's click event or mx:Button's mouseOver event. It only seems to affect the mx:Button's click event. See attached application. The secondary window may be opened any number of times and closed by the "hover close" button or the "label close" label without a leak. Once the "button close" button is clicked, one copy of the window sticks in memory.

Workaround (if any):