flex-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christofer Dutz (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLEX-34648) [BLAZEDS]Memory Leak occurred in AsyncMessage when sending alot of
Date Tue, 28 Jul 2015 14:11:05 GMT

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

Christofer Dutz commented on FLEX-34648:

YESSSSS!!!!! Big breakthrough !!!!

Today I think I created a little project that is able to reproduce the error. It consists
of a Java Server with BlazeDS and a Flex Client. The server sets up a BlazeDS server with
one destination. I also defined a MassMessage producer that simply generates one AsyncMessage
every millisecond containing a random Double value.

On the Client side I have a Flex client that subscribes to this Destination. As long as the
client is running I can see the memory consumption can be cleared, but as soon as I simply
kill the flashplayer, the memory isn't freed again. Now it seems BlazeDS is putting new messages
into the "message bin" of the client. But the only place where it could be removed again (The
flush method of the FlexClientOutboundQueueProcessor) is never again called, while the add
method is called every millisecond. So I guess this is definitely a problematic thing. But
now that I've created a sample application that provokes the problem in a controlled environment,
coming up with a solution shouldn't be that difficult.

> [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