incubator-flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mansour Blanco (JIRA)" <>
Subject [jira] [Created] (FLEX-33139) HTTPService memory leak using both resultFormat e4x and xml
Date Wed, 18 Jul 2012 15:02:34 GMT
Mansour Blanco created FLEX-33139:

             Summary: HTTPService memory leak using both resultFormat e4x and xml
                 Key: FLEX-33139
             Project: Apache Flex
          Issue Type: Bug
          Components: RPC: HTTPService
    Affects Versions: Adobe Flex SDK 4.6 (Release)
            Reporter: Mansour Blanco
            Priority: Critical

Steps to reproduce: 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
 Actual Results:
  UrlLoader is accumulating String objects on each refresh of data which cannot be GC .
  HTTPService cause memory leak calling UrlLoader.
Expected Results:

    How can i avoid memory leak using HTTPService. 

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message