-
Notifications
You must be signed in to change notification settings - Fork 102
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
Gtk portal has excessive resident memory usage #373
Comments
So, I kept an eye on this and have found that the memory use grows slowly, over time. I have also found that the leak(?) occurs when the portal implementation keeps looping doing following syscalls (this looping kind of behaviour occurs sporadically, I don't know what triggers it yet, seems to happen very arbitrarily)
I'm not sure whom the portal is sending messages to or whom it is receiving them from, but it would continue even after I quit all of the applications, so I presume its sending stuff from itself to itself or something similar. There is no traffic on the session dbus when this is happening. https://share.firefox.dev/3JATha3 is a profile I grabbed of the process during this sendmsg/recvmsg spam but it doesn't seem super revealing. |
I found it using in excess of 100MiB of resident memory. For a glue application that is intended to expose a couple dbus endpoints and show file access dialogs, 100M seems quite a lot.
After restarting it drops down to 8.2MiB which is still quite a lot, but palatable.
Advise on what to look into the next time I find the portal consuming significant memory would be great.
The text was updated successfully, but these errors were encountered: