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

Valgrind detects some memleaks #81

Open
FedeDP opened this issue Mar 31, 2019 · 3 comments
Open

Valgrind detects some memleaks #81

FedeDP opened this issue Mar 31, 2019 · 3 comments
Labels
building problems building ddcutil

Comments

@FedeDP
Copy link

FedeDP commented Mar 31, 2019

Hi!
It seems like latest ddcutil (0.9.5) C api has some memleaks;
this is the output of a single run of my own program when built with ddcutil support:
ddcutil_leak.txt

Note that when building without ddcutil, no leak is shown.
Hopefully this will help you, thanks for this software!

@FedeDP
Copy link
Author

FedeDP commented Mar 31, 2019

Moreover, this is just a plain "run program; wait; ctrl-c it (a signalfd is in place, so clean exit)".
It seems like there is some library init function marked with a __attribute__((constructor)) that allocates some memory that is not freed by its destructor.

@rockowitz
Copy link
Owner

rockowitz commented Apr 3, 2019 via email

@FedeDP
Copy link
Author

FedeDP commented Apr 3, 2019

I see; even if i know they are not proper "memleaks", i always find it a good design to actually free memory, even before program's exit. But that's me, and my fixation :D
Feel free to close this one if you feel!

@rockowitz rockowitz added the building problems building ddcutil label May 9, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
building problems building ddcutil
Projects
None yet
Development

No branches or pull requests

2 participants