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

Posted to issues@ignite.apache.org by "Roman Puchkovskiy (Jira)" <ji...@apache.org> on 2024/05/13 09:30:00 UTC

[jira] [Updated] (IGNITE-22210) IgniteImpl leaks in tests due to unclosed DBOptions in SharedRocksDbInstance

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

Roman Puchkovskiy updated IGNITE-22210:
---------------------------------------
    Description: DBOptions used in SharedRocksDbInstance is not closed when SharedRocksDbInstance gets closed, so RocksDbFlushListener (held inside DBOptions) serves as a JNI GC root for IgniteImpl instances. Test suites that start and stop many IgniteImpl instances cause a lot of heap memory being hogged.

> IgniteImpl leaks in tests due to unclosed DBOptions in SharedRocksDbInstance
> ----------------------------------------------------------------------------
>
>                 Key: IGNITE-22210
>                 URL: https://issues.apache.org/jira/browse/IGNITE-22210
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Roman Puchkovskiy
>            Assignee: Roman Puchkovskiy
>            Priority: Major
>              Labels: ignite-3
>             Fix For: 3.0.0-beta2
>
>
> DBOptions used in SharedRocksDbInstance is not closed when SharedRocksDbInstance gets closed, so RocksDbFlushListener (held inside DBOptions) serves as a JNI GC root for IgniteImpl instances. Test suites that start and stop many IgniteImpl instances cause a lot of heap memory being hogged.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)