-
Notifications
You must be signed in to change notification settings - Fork 2
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
yumex_updater_systray memory leak (dnf5) #80
Comments
How to reproduce sudo dnf install python3-memray cd to git checkout make memray-updater-live In a terminal run dbus-send --session --print-reply --dest=dk.yumex.UpdateService /dk/yumex/UpdateService dk.yumex.UpdateService.RefreshUpdates boolean:false
dbus-send --session --print-reply --dest=dk.yumex.UpdateService /dk/yumex/UpdateService dk.yumex.UpdateService.RefreshUpdates boolean:false
dnf5 clean expire-cache
dbus-send --session --print-reply --dest=dk.yumex.UpdateService /dk/yumex/UpdateService dk.yumex.UpdateService.RefreshUpdates boolean:false watch the heap memory dont settle at the same level if metadata is refreshed |
timlau
added a commit
that referenced
this issue
Jun 24, 2024
testing using the build-in metadata expire dbus-send --session --print-reply --dest=dk.yumex.UpdateService /dk/yumex/UpdateService dk.yumex.UpdateService.RefreshUpdates boolean:true |
Looks like it is a memory leak in dnf5 |
created dnf5 upstream issue |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When running an update check with expired metadata not all allocated memory is released after the check is executed.
It is not only when running the build-in metadata expire, running
also trigger the issue, every time metadata is downloaded during the check then a little extra memory is used.
The text was updated successfully, but these errors were encountered: