[ 
https://issues.apache.org/jira/browse/FLEX-33139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mansour Blanco updated FLEX-33139:
----------------------------------

    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.

  was:
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
 
 Actual Results:
 
  UrlLoader is accumulating String objects on each refresh of data which cannot 
be GC .

The attached screenshot shows the URLLoder string variables.

  HTTPService cause memory leak calling UrlLoader.
Expected Results:

    How can i avoid memory leak using HTTPService. 

    
> HTTPService memory leak using both resultFormat e4x and xml
> -----------------------------------------------------------
>
>                 Key: FLEX-33139
>                 URL: https://issues.apache.org/jira/browse/FLEX-33139
>             Project: Apache Flex
>          Issue Type: Bug
>          Components: RPC: HTTPService
>    Affects Versions: Adobe Flex SDK 4.6 (Release)
>            Reporter: Mansour Blanco
>            Priority: Critical
>              Labels: memory_leak
>         Attachments: UrlLoaderString.PNG, XLC.zip
>
>
> 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.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to