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 Thu, 11 Jun 2015 13:01:00 GMT

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

Christofer Dutz commented on FLEX-34648:

Thank you for this detailed report ... I have come across something similar some time ago
but didn't have the time to investigate it any further. Now that we have the parity-release
(even if there is some discussion on the list if it actually is a parity release) out, we
can start working on improving BlazeDS ... your findings will definitely help tracking down
the problem. 

I'm going to grab the issue cause I would really like to start fixing this as soon as possible.
But I won't be able to in the really close future ... will take a few days till I can spare
some time. So if anyone else wants to start working on this, please grab it. I just don't
want to forget it.

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