-
Notifications
You must be signed in to change notification settings - Fork 66
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 reports allocated mem at close #67
Comments
It's probably caused by |
If you still have that code, can you post the valgrind output? That line with Sorry for the delayed response. I haven't had time for |
Hi, no problem! The output is in the <details> tag, unless you mean something else? |
Whoops! I guess I missed that. Digging through this, I'm noticing how ugly my old code is and remembering that I was rushing to get it working at the time, but in the process, I remembered something that I was fighting with when I wrote the code. There was an issue somebody opened a long time ago in which While I was making this change, something strange happened. I wrote the destructor for I used Judging by the valgrind output, it looks like |
I'm not sure it's such a major problem to be honest, maybe just leave the issue open? |
I ran valgrind on some code I had written and found that some memory isn't deallocated on close. This probably doesn't matter unless you keep closing/opening the X lib a LOT, but it's nice to tidy up after ourselves ;). I used x11_dl, haven't checked x11.
Of course it might be a leak in X, or some mem that can only be allocated once, in which case it doesn't matter.
Valgrind report
The text was updated successfully, but these errors were encountered: