[
https://issues.apache.org/jira/browse/FLEX-34648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14611909#comment-14611909
]
Christofer Dutz commented on FLEX-34648:
----------------------------------------
Currently I'm sort of stuck in beaurocratic stuff for ApacheCon EU 2015 as soon
as I get some air I'll address this ... I had the exact same problems you are
having and I am also really interested in having this fixed. What would help a
lot would be if one of you would volunteer to create a mini test project that
reproduces this problem. Then I'll definitely manage to squeeze the fix in a
lot faster.
> [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: [email protected]
> 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)
