You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flex.apache.org by "Mansour Blanco (JIRA)" <ji...@apache.org> on 2012/07/19 09:39:36 UTC
[jira] [Comment Edited] (FLEX-33139) HTTPService memory leak using
both resultFormat e4x and xml
[ https://issues.apache.org/jira/browse/FLEX-33139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13417318#comment-13417318 ]
Mansour Blanco edited comment on FLEX-33139 at 7/19/12 7:38 AM:
----------------------------------------------------------------
Not in this testcase, but I tried calling disposeXML() but it didn't fix the problem. There is an attached picture that shows the strings references by the internal call for URLLoader by HTTPService
was (Author: mansuro):
Not in this testcasem but I tried calling disposeXML() but it didn't fix the problem. There is an attached picture that shows the strings references by the internal call for URLLoader by 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