[
https://issues.apache.org/jira/browse/FLEX-34648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14641962#comment-14641962
]
Srinath H S commented on FLEX-34648:
------------------------------------
My thoughts on the issue.
The memory leak is due to accumulation of large amounts of AsyncMessages which
are not delivered, the Flexclient holds all of them in a list and keeps them
forever. This can be solved by few overrides from my solution here
http://in-finite.me/fixing-blazeds-polling-amf-memory-leak
However the bigger issue is due to FlexClients not being closed. Upon closer
look it turns out the current blazeds code waits for "timeout-minutes" and then
invalidates the FlexClients. However in our previous test runs the FlexClient
never gets GC. This can be easily reproduced it happens when client "suddenly"
vanishes / stops polling. That will be due to user directly closing the browser.
> [BLAZEDS]Memory Leak occurred in AsyncMessage when sending alot of
> -------------------------------------------------------------------
>
> Key: FLEX-34648
> URL: https://issues.apache.org/jira/browse/FLEX-34648
> Project: Apache Flex
> Issue Type: Bug
> Components: BlazeDS
> Affects Versions: BlazeDS 4.7
> Reporter: ibrahem.sha...@gmail.com
> Assignee: Christofer Dutz
> Priority: Critical
>
> a memory leak occurred when sending alot of AsyncMessage through BLAZEDS in a
> real time systems which is heavilly using messaging however we are increasing
> the jvm heap size to 4 GB 80% of the size is occupied by AsyncMessage
> objects this is very clear from the generated heap dump.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
