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

Posted to dev@ignite.apache.org by "Pavel Tupitsyn (JIRA)" <ji...@apache.org> on 2018/10/01 17:08:00 UTC

[jira] [Created] (IGNITE-9757) С++: DetachCurrentThread is never called, causing Java thread leak

Pavel Tupitsyn created IGNITE-9757:
--------------------------------------

             Summary: С++: DetachCurrentThread is never called, causing Java thread leak
                 Key: IGNITE-9757
                 URL: https://issues.apache.org/jira/browse/IGNITE-9757
             Project: Ignite
          Issue Type: Bug
          Components: platforms
            Reporter: Pavel Tupitsyn
            Assignee: Igor Sapego


JNI method AttrachCurrentThread must be called on every thread that performs JNI calls.
This causes Thread object to be created on Java side, with a bunch of thread-local values (both managed and unmanaged). To clean this up we must call DetachCurrentThread JNI method.

Ignite C++ seems to never do this. Same issue as IGNITE-9638 for .NET, known to cause OOM in a scenario where lots of threads are created and destroyed.



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