ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nikolay Izhikov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-9638) .NET: JVM keeps track of CLR Threads, even when they are finished
Date Fri, 28 Sep 2018 06:24:00 GMT

    [ https://issues.apache.org/jira/browse/IGNITE-9638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16631415#comment-16631415

Nikolay Izhikov commented on IGNITE-9638:

Hello, [~ptupitsyn], [~ilyak].

Can we move this ticket to 2.8 release?

> .NET: JVM keeps track of CLR Threads, even when they are finished 
> ------------------------------------------------------------------
>                 Key: IGNITE-9638
>                 URL: https://issues.apache.org/jira/browse/IGNITE-9638
>             Project: Ignite
>          Issue Type: Bug
>          Components: platforms
>    Affects Versions: 2.6
>            Reporter: Ilya Kasnacheev
>            Assignee: Pavel Tupitsyn
>            Priority: Major
>              Labels: .NET
>             Fix For: 2.7
>         Attachments: IgniteRepro.zip
> When you create a Thread in C#, JVM creates corresponding thread "Thread-NNNN" which
is visible in jstack. When C# joins this thread, it is not removed from JVM and is kept around.
This means that jstack may show thousands of threads which are not there. Reproducer is attached.
It is presumed that memory will be exhausted eventually.

This message was sent by Atlassian JIRA

View raw message