Skip to content
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

Goldwarden spawns python processes until pc crash or processes are manually killed #218

Closed
ghandigarcia opened this issue May 15, 2024 · 6 comments
Assignees
Labels
bug Something isn't working needs testing

Comments

@ghandigarcia
Copy link

Hey, big fan of this project since I came across it a few months ago!

I have a bit of an issue that I think is related to Goldwarden, though I'm not entirely sure. I also have messed something up somewhere, that's always a possibility :)

It is the only application that I have installed with python code that I've found to cause the following behavior;
with Goldwarden auto-starting on boot, or when starting it via either gui or CLI, a number of python processes roughly ~8mb in size starts being spawned. They keep spawning until the laptop either crashes or I manually kill the processes.
Screencast from 15-05-24 14:54:10.webm

Screenshot of what it looks like when I run flatpak run com.quexten.Goldwarden
Screenshot from 2024-05-15 15-25-42

@hulloanson
Copy link

hulloanson commented May 24, 2024

Same experience here. There were upward of 100s of status.py processes when I checked and killing them gave me back 14GiB of memory.

Running flatpak installation v0.3.2, launched with unmodified desktop entry.

Edit: grammar and install info

@quexten
Copy link
Owner

quexten commented May 25, 2024

What desktop environment are you on?

@quexten quexten self-assigned this May 25, 2024
@quexten quexten added bug Something isn't working needs testing labels May 25, 2024
@quexten
Copy link
Owner

quexten commented May 25, 2024

#223 should fix this. I think your de does not implement the background portal (or just v1), and so the status setting dbus call fails, and the process never exits, just idling. Since status.py is spawned quite frequently (and expected to exit immediately), this causes the mess you are seeing.

@ghandigarcia
Copy link
Author

What desktop environment are you on?

I'm on Gnome, version 42.9. Let me know if there's anything else you need or if you'd like me to test something. I'll do my best to help!

@hulloanson
Copy link

hulloanson commented May 26, 2024

#223 should fix this. I think your de does not implement the background portal (or just v1), and so the status setting dbus call fails, and the process never exits, just idling. Since status.py is spawned quite frequently (and expected to exit immediately), this causes the mess you are seeing.

Did find these in logs when running goldwarden gui in cli with flatpak run.

g-dbus-error-quark: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface “org.freedesktop.portal.Background” on object at path /org/freedesktop/portal/desktop (19)

I was using LXDM with openbox.

Copying the fix in #223 to the flatpak installation did fix the issue. Kudos to the quick resolution!

@ghandigarcia
Copy link
Author

Just tested the fix in #223 as well, it looks all good now. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working needs testing
Projects
None yet
Development

No branches or pull requests

3 participants