You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2015/09/24 09:44:04 UTC

[jira] [Commented] (FELIX-5051) Memory leak in async delivery

    [ https://issues.apache.org/jira/browse/FELIX-5051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14905960#comment-14905960 ] 

Carsten Ziegeler commented on FELIX-5051:
-----------------------------------------

[~gnt] I've committed a potential fix in rev 1705009

> Memory leak in async delivery
> -----------------------------
>
>                 Key: FELIX-5051
>                 URL: https://issues.apache.org/jira/browse/FELIX-5051
>             Project: Felix
>          Issue Type: Bug
>    Affects Versions: eventadmin-1.4.2, eventadmin-1.4.4
>            Reporter: Guillaume Nodet
>            Assignee: Guillaume Nodet
>             Fix For: eventadmin-1.4.6
>
>
> From debugging through the code, it seems that entries get added to the org.apache.felix.eventadmin.impl.tasks.AsyncDeliverTasks#m_running_threads  (java.util.concurrent.ConcurrentHashMap) but not removed. 
> In org.apache.felix.eventadmin.impl.tasks.AsyncDeliverTasks.TaskExecuter#run() the call to remove is trying to remove the "object" rather than the key. This does not remove anything from the map. 
> {code}
>   public void run()
>         {
>           ...
>                         this.m_running_threads.remove(this);
>            ...
>             } while ( running );
>         }
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)