You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@mina.apache.org by "Alexander B (JIRA)" <ji...@apache.org> on 2018/04/16 07:13:00 UTC

[jira] [Closed] (DIRMINA-1081) Increasing number of ConcurrentLinkedQueue$Node objects

     [ https://issues.apache.org/jira/browse/DIRMINA-1081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alexander B closed DIRMINA-1081.
--------------------------------
    Resolution: Not A Bug

> Increasing number of ConcurrentLinkedQueue$Node objects
> -------------------------------------------------------
>
>                 Key: DIRMINA-1081
>                 URL: https://issues.apache.org/jira/browse/DIRMINA-1081
>             Project: MINA
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.0.16, 2.0.17
>            Reporter: Alexander B
>            Priority: Major
>         Attachments: heap.png, linkedqueuenodes.png, recorded live allocations.png
>
>
> In a few issues i read, that some users detect a hugh number of ConcurrentLinkedQueue$Node objects, which are actually not collected by GC. I dont know if this behaviour is still an open bug, so i opened this new issue.
> Attached are two screenshot made by JProfiler. It seems, that the broadcast method references these objects and does not deallocate them.
> In my point of view this behaviour was getting better by using version 2.0.17 instead of 2.0.16, but this behaviour still exists.
>  
> PS:  I am using Java 1.8.0_161b12 64bit
>  
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)