-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Linux: init & close cause 2 not-freed blocks #231
Comments
My first guess would be to look at the hotplug thread. |
I definitely believe this is a libudev issue. You can file an issue against that library if you'd like, referencing this issue for details.
|
I have observed the exact same issue in my valgrind output - sounds like there isn't a solution? |
As reported in fedora this is not an actual leak, but an effect of some allocation cache used by udev: https://bugzilla.redhat.com/show_bug.cgi?id=1280334 The following suppression file can be used to silence the issue when profiling libusb programs:
Maybe something like this into a Ciao, |
I don't understand why a simple init & close causes at least 2 not-freed blocks. Any lead ?
I am pretty sure this issue was mentioned but unfortunately haven't found yet.
The result is the same with the examples on the repo.
Nothing to report with LIBUSB_LOG_LEVEL_DEBUG set.
Plateform: Archlinux x86_64
Libusb: v1.0.21-1
Thank you.
The text was updated successfully, but these errors were encountered: