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

Memory leaks #2

Open
crcox opened this issue Sep 8, 2015 · 2 comments
Open

Memory leaks #2

crcox opened this issue Sep 8, 2015 · 2 comments

Comments

@crcox
Copy link
Owner

crcox commented Sep 8, 2015

valgrid --leak-check=full ./Lens will reveal many. Need to add/register ExitProcs.

@crcox
Copy link
Owner Author

crcox commented Sep 21, 2015

It turns out that these are generally unproblematic. Most originate from functions in the Tcl/Tk libraries. The ones that don't either are recoverable by the OS, or are trivial. They should still be handled, but they are not a barrier to use.

Valgrind summary:

==6171==    definitely lost: 111 bytes in 3 blocks
==6171==    indirectly lost: 0 bytes in 0 blocks
==6171==      possibly lost: 1,928,208 bytes in 52 blocks
==6171==    still reachable: 373,958 bytes in 1,388 blocks
==6171==         suppressed: 0 bytes in 0 blocks

@crcox
Copy link
Owner Author

crcox commented Sep 25, 2015

I'd like to know more before actually closing this. Another set of eyes on the issue would be invaluable.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant