-
Notifications
You must be signed in to change notification settings - Fork 87
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG?]: High memory consumption - spawn too many system threads for image/thumbnail decoding & leaking? #641
Comments
l-const
changed the title
[BUG?]: High memory consumption - memory leak?
[BUG?]: High memory consumption - spawn too many system threads?
Nov 4, 2024
l-const
changed the title
[BUG?]: High memory consumption - spawn too many system threads?
[BUG?]: High memory consumption - spawn too many system threads for image/thumbnail decoding?
Nov 4, 2024
Update:
heaptrack.cosmic-files.28551.zip actually, cosmic_text seems to be leaking, reported 300MB : heaptrack.cosmic-files.40307.zip
|
l-const
changed the title
[BUG?]: High memory consumption - spawn too many system threads for image/thumbnail decoding?
[BUG?]: High memory consumption - spawn too many system threads for image/thumbnail decoding & leaking?
Nov 5, 2024
I recorded a small video going from 50MB to 350MB: memory-leak-cosmic-files.webm |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Cosmic-files version:
20f9292
Issue/Bug description:
Steps to reproduce:
Expected behavior:
Other notes:
using heaptrack: https://github.com/KDE/heaptrack
installed with :
executed:
heaptrack --pid ${pid of cosmic-files}
with initial on startup memory consumption of 48MB as seen from this:
reaching up to and excedding 300MB:
heaptrack overview:
it seems that no memory leak is happening but for the thumnail generation
we create through tokio too manu system threads by calling the clone3 system call
Here is the zipped .zst file that i exported:
heaptrack.cosmic-files.31272.zip
The text was updated successfully, but these errors were encountered: