-
Notifications
You must be signed in to change notification settings - Fork 400
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 leakage #322
Comments
These messages are shown because Ricochet builds with AddressSanitizer when available, because it has very useful hardening features. Another thing it does on x86_64 Linux is detect leaked memory and print these messages at exit. Ideally, that feature should be disabled for non-developer builds, because the leak information isn't useful most of the time. These are probably real "leaks", but they appear to all be in other libraries, and many are probably singleton-style allocations that don't get cleaned up - so they're not leaking in any meaningful sense. Unfortunately I can't find a way to disable the leak check automatically. The only method I've found is to have ASAN_OPTIONS=detect_leaks=0 in the environment, but setting this in main() is too late. |
I can say that there's indeed a leak, but is not related to the program closing. If I write something inside the message textbox, the memory will increase every time I write something (including "writing" backspace). |
We no longer have ASAN on release builds (#341), so these messages won't appear. Real leaks should get specific real bugs if they seem to exist. |
hi,
on my system (arch linux, kernel 4.3.3-2), ricochet produces significant memory leaks every time it runs.
for illustration, just launching it and closing immediately produces this:
The text was updated successfully, but these errors were encountered: