Github user franz1981 commented on the issue:
https://github.com/apache/activemq-artemis/pull/1372
@clebertsuconic ``Unpooled::directBuffer`` is not specified on Netty
javadoc but could allocate a direct ``ByteBuffer`` with no ``Cleaner`` in it
i.e. when GC occour the JVM doesn't free it.
Calling directly ``ByteBuffer.allocateDirect`` forces the instantiation of
the buffer with a ``Cleaner``, hence tests, that create and destroy multiple
``TimedBuffer`` instances do not goes OOM anymore.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
