[
https://issues.apache.org/jira/browse/IGNITE-20036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksandr Polovtcev updated IGNITE-20036:
-----------------------------------------
Description: When investigating a different issue regarding an OOM in
tests, I found out that some threads were not stopped in time (OOM was actually
happening in these threads, namely "client-data-streamer-flush" thread and
other client-related threads). I added some code in {{AfterEach}} that checked
if any of these threads were still running and fixed the code to eliminate all
these leaks. Even though that didn't solve the original OOM problem, I still
think the changes might be useful, because they help to avoid thread leaks.
> Fix resources leak in Ignite client tests
> -----------------------------------------
>
> Key: IGNITE-20036
> URL: https://issues.apache.org/jira/browse/IGNITE-20036
> Project: Ignite
> Issue Type: Task
> Reporter: Aleksandr Polovtcev
> Assignee: Aleksandr Polovtcev
> Priority: Major
> Labels: ignite-3
> Time Spent: 10m
> Remaining Estimate: 0h
>
> When investigating a different issue regarding an OOM in tests, I found out
> that some threads were not stopped in time (OOM was actually happening in
> these threads, namely "client-data-streamer-flush" thread and other
> client-related threads). I added some code in {{AfterEach}} that checked if
> any of these threads were still running and fixed the code to eliminate all
> these leaks. Even though that didn't solve the original OOM problem, I still
> think the changes might be useful, because they help to avoid thread leaks.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
