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.

Sign up for GitHub

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

Jump to bottom

Probable memory leak in dasbus server handler #80

Open
wdouglass opened this issue Feb 8, 2022 · 4 comments · May be fixed by #81
Open

Probable memory leak in dasbus server handler #80

wdouglass opened this issue Feb 8, 2022 · 4 comments · May be fixed by #81
Labels
bug Something isn't working

Comments

@wdouglass
Copy link
Contributor

Consider the following script
one.py.txt

If this script is run, and the following loop is run in another (bash) window

while busctl --user call com.carnegierobotics.test /com/carnegierobotics/test com.carnegierobotics.dasbus.test One; do echo "DONE"; done

resident memory seems to grow indefinitely. Not sure if this is a dasbus bug or a glib bug.
@tjoslin
Copy link
Contributor

tjoslin commented Feb 8, 2022

may be related to #75

@wdouglass
Copy link
Contributor Author

investigating glib as a source of this problem
https://gitlab.gnome.org/GNOME/glib/-/merge_requests/2478

if that ends up getting merged to glib, i'll close this issue

@poncovka
Copy link
Contributor

poncovka commented Feb 9, 2022

Thanks for the investigation!

@wdouglass wdouglass linked a pull request Feb 9, 2022 that will close this issue
Open
@tjoslin
Copy link
Contributor

tjoslin commented Feb 9, 2022

#81 resolves the leak that is testable in the one.py script included here. The upstream glib investigation ended up being a red herring.

@poncovka poncovka added the bug Something isn't working label Feb 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Decrement the reference count on the invocation object in _method_callback wdouglass/dasbus
3 participants
@wdouglass @poncovka @tjoslin