You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mina.apache.org by "jpalacios (JIRA)" <ji...@apache.org> on 2018/10/26 02:27:00 UTC
[jira] [Commented] (SSHD-854) Massive object graph in
NioSocketSession
[ https://issues.apache.org/jira/browse/SSHD-854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16664558#comment-16664558 ]
jpalacios commented on SSHD-854:
--------------------------------
NOTE: I realise this issue may be partly (or completely) originated in SSHD so I've created a ticket with them as well: https://issues.apache.org/jira/browse/SSHD-855
> Massive object graph in NioSocketSession
> ----------------------------------------
>
> Key: SSHD-854
> URL: https://issues.apache.org/jira/browse/SSHD-854
> Project: MINA SSHD
> Issue Type: Bug
> Reporter: jpalacios
> Priority: Major
>
> I'm looking at a heap dump from one of our customers where the retained heap size for some {{NioSocketSession}} instances is almost 1GB.
> From the looks of the dump MINA has created a massive object graph where:
> {code}
> NioSocketSession -> SelectionKeyImpl -> EpollSelectorImpl -> HashMap -> SelectionKeyImpl -> NioSocketSession -> ...
> {code}
> From the looks of the obeject IDs these are not loops
> Each individual object is not large by itself but at the top of the graph the accumulated retained size is enough to produce an OOME
> Could you help me understand how MINA can produce such a massive object graph? Should MINA apply any defense mechanism to prevent this??
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)