flex-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mohamed Amer (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLEX-34648) [BLAZEDS]Memory Leak occurred in AsyncMessage when sending alot of
Date Thu, 25 Jun 2015 21:27:06 GMT

    [ https://issues.apache.org/jira/browse/FLEX-34648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14601975#comment-14601975

Mohamed Amer commented on FLEX-34648:

    I'm glad that this bug got some attention.
Just to point out the issue clearly. The memory leak described above occurs while using the
"AMFEndpoint" which extends a BasePollingHTTPEndpoint not the streaming endpoint.

I'd like to thank Robert for his contribution, though the proposed solution by overriding
the method "serviceStreamingRequest" doesn't apply to the AMFEndpoint.
as the call hierarchy of the method is withing the streaming endpoint only.

I have deep wishes that we catch the source of this bug.
Thanks a lot.

> [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.shawky@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

View raw message