[jboss-jira] [JBoss JIRA] (WFLY-4187) Cloning org.jboss.invocation.InterceptorContext leaks memory

[Eduardo Martins (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-4187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13059390#comment-13059390 ] 

Eduardo Martins commented on WFLY-4187:
---------------------------------------

This was fixed by JBoss Invocation 1.4.1.Final, which will be integrated in this week WildFly Core 1.0.0.Beta5 release, and that should mean the issue will be fixed in next WildFly 9.0.0 release. I will keep an eye on it and close the issue when WildFly master has the fixed JBoss Invocation integrated.

In case you want WildFly 8.x with such fix you need to upgrade JBoss Invocation to 1.4.1.Final or, in case its not fully compatible, fork the tag of the included JBoss Invocation, and apply https://github.com/jbossas/jboss-invocation/commit/21cbe4d6d08d245ac80efe13c959a8a91acf5b19 

> Cloning org.jboss.invocation.InterceptorContext leaks memory
> ------------------------------------------------------------
>
>                 Key: WFLY-4187
>                 URL: https://issues.jboss.org/browse/WFLY-4187
>             Project: WildFly
>          Issue Type: Bug
>    Affects Versions: 8.1.0.Final, 8.2.0.Final
>            Reporter: Jeroen Wielandt
>            Assignee: Eduardo Martins
>
> The clone function uses sublist  to set the new list of interceptors. 
> public InterceptorContext clone() {
>      ....
>         clone.setInterceptors(interceptors.subList(next, interceptors.size()));
>         return clone;
>     }
> This will keep a reference to the original list around. So the original list will never be released. Chaining clone multiple times will eventually cause an out of memory because each sublist grows slightly.



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)