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/18 17:02:34 UTC
[jira] [Created] (FLEX-33139) HTTPService memory leak using both
resultFormat e4x and xml
Mansour Blanco created FLEX-33139:
-------------------------------------
Summary: 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
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 .
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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (FLEX-33139) HTTPService memory leak using both
resultFormat e4x and xml
Posted by "Mansour Blanco (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FLEX-33139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mansour Blanco updated FLEX-33139:
----------------------------------
Comment: was deleted
(was: This requires player changes, for more details: https://issues.apache.org/jira/browse/FLEX-11520)
> 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, testUsingE4x.mxml
>
>
> 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
[jira] [Commented] (FLEX-33139) HTTPService memory leak using both
resultFormat e4x and xml
Posted by "Alex Harui (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FLEX-33139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13417306#comment-13417306 ]
Alex Harui commented on FLEX-33139:
-----------------------------------
I haven't looked at your test case. Is it calling dispose()?
> 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
[jira] [Commented] (FLEX-33139) HTTPService memory leak using both
resultFormat e4x and xml
Posted by "Saber Chebka (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FLEX-33139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13418979#comment-13418979 ]
Saber Chebka commented on FLEX-33139:
-------------------------------------
Very SIMILAR TO...
> 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, testUsingE4x.mxml
>
>
> 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
[jira] [Updated] (FLEX-33139) HTTPService memory leak using both
resultFormat e4x and xml
Posted by "Mansour Blanco (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FLEX-33139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mansour Blanco updated FLEX-33139:
----------------------------------
Attachment: UrlLoaderString.PNG
> 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
>
> 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Comment Edited] (FLEX-33139) HTTPService memory leak using
both resultFormat e4x and xml
Posted by "Mansour Blanco (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FLEX-33139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13418143#comment-13418143 ]
Mansour Blanco edited comment on FLEX-33139 at 7/19/12 10:08 AM:
-----------------------------------------------------------------
I've tried with URLLoader and the leak is still there
was (Author: mansuro):
I've tried with URLLoader and there is no leak.
> 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
[jira] [Commented] (FLEX-33139) HTTPService memory leak using both
resultFormat e4x and xml
Posted by "Saber Chebka (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FLEX-33139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13418820#comment-13418820 ]
Saber Chebka commented on FLEX-33139:
-------------------------------------
Very possible duplicate of http://bugs.adobe.com/jira/browse/SDK-11982 or http://bugs.adobe.com/jira/browse/SDK-11982, status of resolution stays as "cannot fix" and "differed".
Reporter offers 4 testcase where only one is provoking a memory leak.
I tested them all and that was as expected.
Cases:
1. format ="xml" file="leaktest.xml" -> It does not leak.
2. format ="xml" file="pbentries.xml" -> It does not leak.
3. format ="e4x" file="leaktest.xml" -> It does not leak.
4. format ="e4x" file="pbentries.xml" -> It leaks.
As a workaraound:
1- Reloading the app frees the memory.
2- Walking into one of the 3 non leak test cases
> 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
[jira] [Updated] (FLEX-33139) HTTPService memory leak using both
resultFormat e4x and xml
Posted by "Mansour Blanco (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FLEX-33139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mansour Blanco updated FLEX-33139:
----------------------------------
Attachment: XLC.zip
> 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: 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
>
> 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (FLEX-33139) HTTPService memory leak using both
resultFormat e4x and xml
Posted by "Mansour Blanco (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FLEX-33139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13417318#comment-13417318 ]
Mansour Blanco commented on FLEX-33139:
---------------------------------------
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
[jira] [Commented] (FLEX-33139) HTTPService memory leak using both
resultFormat e4x and xml
Posted by "Alex Harui (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FLEX-33139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13418983#comment-13418983 ]
Alex Harui commented on FLEX-33139:
-----------------------------------
Adobe bugs have been migrated to Apache. SDK-11982 is FLEX-11520. Please don't re-file bugs from Adobe JIRA.
> 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, testUsingE4x.mxml
>
>
> 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
[jira] [Closed] (FLEX-33139) HTTPService memory leak using both
resultFormat e4x and xml
Posted by "Mansour Blanco (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FLEX-33139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mansour Blanco closed FLEX-33139.
---------------------------------
Resolution: Fixed
This requires player changes, for more details: https://issues.apache.org/jira/browse/FLEX-11520
> 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, testUsingE4x.mxml
>
>
> 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
[jira] [Comment Edited] (FLEX-33139) HTTPService memory leak using
both resultFormat e4x and xml
Posted by "Mansour Blanco (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Commented] (FLEX-33139) HTTPService memory leak using both
resultFormat e4x and xml
Posted by "Alex Harui (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FLEX-33139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13417226#comment-13417226 ]
Alex Harui commented on FLEX-33139:
-----------------------------------
Have you tried an ActionScript-only test case with just URLLoader? If it leaks then the problem is in the player and not HTTPService.
Keep in mind that it is possible that the strings are associated with the on-the-fly parsing of the XML and will get cleaned up by a call to dispose() or may be referenced by the Profiler itself. The best test case may be to not use the profiler and loop through a sequence of calls and see if memory hits an upper bound or grows forever
> 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
[jira] [Commented] (FLEX-33139) HTTPService memory leak using both
resultFormat e4x and xml
Posted by "Mansour Blanco (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FLEX-33139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13417301#comment-13417301 ]
Mansour Blanco commented on FLEX-33139:
---------------------------------------
I haven't tried the URLLoader case, but I used the task manager to check the memory and it keeps on increasing all the time.
> 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
[jira] [Updated] (FLEX-33139) HTTPService memory leak using both
resultFormat e4x and xml
Posted by "Mansour Blanco (JIRA)" <ji...@apache.org>.
[ 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
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.
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 .
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
>
> 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.
--
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
[jira] [Updated] (FLEX-33139) HTTPService memory leak using both
resultFormat e4x and xml
Posted by "Mansour Blanco (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Commented] (FLEX-33139) HTTPService memory leak using both
resultFormat e4x and xml
Posted by "Mansour Blanco (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FLEX-33139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13418143#comment-13418143 ]
Mansour Blanco commented on FLEX-33139:
---------------------------------------
I've tried with URLLoader and there is no leak.
> 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
[jira] [Commented] (FLEX-33139) HTTPService memory leak using both
resultFormat e4x and xml
Posted by "Saber Chebka (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FLEX-33139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13418846#comment-13418846 ]
Saber Chebka commented on FLEX-33139:
-------------------------------------
Mansour, back to the example you provided, on function "resultHTTP(event:ResultEvent)", after getting used the xml data result, I added next code snippets:
// Dispose the XML for gc, the force the garbage collection
System.disposeXML(xmlData);
xmlData = null;
gc_perform(event);
gc_perform(event);
where gc_perform() is the gc forcer method:
private function gc_perform(event:Event):void
{
// Garbage Collection
try
{
new LocalConnection().connect('foo');
new LocalConnection().connect('foo');
}
catch(e:*)
{
}
memory.text=(System.totalMemory/(1024*1024))+" Mb"
}
// Some other workaround was done on function updateXMLC() to make it look like:
// TRY NOT TO RE USE THE HTTP SERVICE ONCE AGAIN
private function updateXMLC(event:TimerEvent):void
{
if(httpS){
httpS.removeEventListener(ResultEvent.RESULT, resultHTTP);
httpS.clearResult(true);
httpS.disconnect();
httpS = null;
}
httpS = new HTTPService();
httpS.url = "data.xml";
httpS.addEventListener(ResultEvent.RESULT, resultHTTP);
httpS.resultFormat="e4x";
httpS.send();
}
==> As a result: Memory Leak seems to be disapeared.
I know the use of gc forcer method is not advised, but it seems to be the key for a non solved issue by Adobe.
> 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
[jira] [Closed] (FLEX-33139) HTTPService memory leak using both
resultFormat e4x and xml
Posted by "Mansour Blanco (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FLEX-33139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mansour Blanco closed FLEX-33139.
---------------------------------
Resolution: Fixed
> 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, testUsingE4x.mxml
>
>
> 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
[jira] [Commented] (FLEX-33139) HTTPService memory leak using both
resultFormat e4x and xml
Posted by "Mansour Blanco (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FLEX-33139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13418977#comment-13418977 ]
Mansour Blanco commented on FLEX-33139:
---------------------------------------
It's not a duplicate, this is not Adobe JIRA
> 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, testUsingE4x.mxml
>
>
> 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
[jira] [Reopened] (FLEX-33139) HTTPService memory leak using both
resultFormat e4x and xml
Posted by "Mansour Blanco (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FLEX-33139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mansour Blanco reopened FLEX-33139:
-----------------------------------
> 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, testUsingE4x.mxml
>
>
> 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
[jira] [Updated] (FLEX-33139) HTTPService memory leak using both
resultFormat e4x and xml
Posted by "Saber Chebka (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FLEX-33139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Saber Chebka updated FLEX-33139:
--------------------------------
Attachment: testUsingE4x.mxml
Changes on testUsingE4x.mxml file , please test for confirming
> 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, testUsingE4x.mxml
>
>
> 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