You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@fury.apache.org by "xiaxianggo (via GitHub)" <gi...@apache.org> on 2024/12/25 09:48:15 UTC
[D] Does Fury have a memory leak? I've submitted many tasks to the thread pool, and even after the tasks are completed, the memory has not been released. [fury]
GitHub user xiaxianggo created a discussion: Does Fury have a memory leak? I've submitted many tasks to the thread pool, and even after the tasks are completed, the memory has not been released.
<img width="1233" alt="image" src="https://github.com/user-attachments/assets/008efb29-3845-4e56-9e8a-ddc39f2a1c43" />
GitHub link: https://github.com/apache/fury/discussions/1989
----
This is an automatically sent email for commits@fury.apache.org.
To unsubscribe, please send an email to: commits-unsubscribe@fury.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@fury.apache.org
For additional commands, e-mail: commits-help@fury.apache.org
Re: [D] Does Fury have a memory leak? I've submitted many tasks to the thread pool, and even after the tasks are completed, the memory has not been released. [fury]
Posted by "xiaxianggo (via GitHub)" <gi...@apache.org>.
GitHub user xiaxianggo edited a discussion: Does Fury have a memory leak? I've submitted many tasks to the thread pool, and even after the tasks are completed, the memory has not been released.
<img width="1233" alt="image" src="https://github.com/user-attachments/assets/2e09bc05-1377-4e1b-84a1-53c2c40e837d" />
GitHub link: https://github.com/apache/fury/discussions/1989
----
This is an automatically sent email for commits@fury.apache.org.
To unsubscribe, please send an email to: commits-unsubscribe@fury.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@fury.apache.org
For additional commands, e-mail: commits-help@fury.apache.org
Re: [D] Does Fury have a memory leak? I've submitted some tasks to the thread pool, and even after the tasks are completed, the memory has not been released. [fury]
Posted by "xiaxianggo (via GitHub)" <gi...@apache.org>.
GitHub user xiaxianggo edited a discussion: Does Fury have a memory leak? I've submitted some tasks to the thread pool, and even after the tasks are completed, the memory has not been released.
<img width="1233" alt="image" src="https://github.com/user-attachments/assets/2e09bc05-1377-4e1b-84a1-53c2c40e837d" />
GitHub link: https://github.com/apache/fury/discussions/1989
----
This is an automatically sent email for commits@fury.apache.org.
To unsubscribe, please send an email to: commits-unsubscribe@fury.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@fury.apache.org
For additional commands, e-mail: commits-help@fury.apache.org
Re: [D] Does Fury have a memory leak? I've submitted some tasks to the thread pool, and even after the tasks are completed, the memory has not been released. [fury]
Posted by "xiaxianggo (via GitHub)" <gi...@apache.org>.
GitHub user xiaxianggo closed a discussion: Does Fury have a memory leak? I've submitted some tasks to the thread pool, and even after the tasks are completed, the memory has not been released.
<img width="1233" alt="image" src="https://github.com/user-attachments/assets/2e09bc05-1377-4e1b-84a1-53c2c40e837d" />
GitHub link: https://github.com/apache/fury/discussions/1989
----
This is an automatically sent email for commits@fury.apache.org.
To unsubscribe, please send an email to: commits-unsubscribe@fury.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@fury.apache.org
For additional commands, e-mail: commits-help@fury.apache.org