[FLEX-33139] HTTPService memory leak using both resultFormat e4x and xml

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: Adobe Flex SDK 4.6 (Release)
• Component/s: RPC: HTTPService
• Labels: memory_leak
• Assignee: Unassigned
• Reporter: Mansour Blanco
• Created: 18/Jul/12 15:01
• Updated: 20/Jul/12 07:46
• Resolved: 20/Jul/12 07:46

Description

Steps to reproduce:
1.download the zip file
2.import as a project
3.profile using e4x or xml resultFormat
4.create 2 memory snapshots from the Flex profiler
5.use "Find Loitering Object" View between the 2 snapshots.
6.analyse String objects using "Open Objects Reference"

Note : Forcing GC cannot remove Loitering String Objects

UrlLoader is accumulating String objects on each refresh of data which cannot be GC .
The attached screenshot shows the URLLoder string variables.