<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - 'message's in ctx->Debug.LogMessages[] seem to leak." href="https://bugs.freedesktop.org/show_bug.cgi?id=98281#c4">Comment # 4</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - 'message's in ctx->Debug.LogMessages[] seem to leak." href="https://bugs.freedesktop.org/show_bug.cgi?id=98281">bug 98281</a> from <a class="email" href="mailto:eero.t.tamminen@intel.com" title="Eero Tamminen <eero.t.tamminen@intel.com>"> Eero Tamminen</a> <pre>(In reply to Suzuki, Shinji from <a href="show_bug.cgi?id=98281#c2">comment #2</a>) > The amount of memory being in use may be bounded. But I believe there are > blocks that don't get released until process termination. Having unreleased > memory brings bad user experience to users of valgrind or any kind of memory > debugging tools. While libraries should not leak even in their destroy/exit functions... If you just want to debug run-time leaks instead of things leaked in the application termination procedure, there's a way to do that with Valgrind. Just terminate the program with a signal that Valgrind can catch, but the program itself doesn't (e.g. SIGBUS, SIGXCPU or SIGTRAP are rarely caught by programs, but Valgrind catches etc). That way program's termination code (and any library functions called by it) cannot leak memory, and Valgrind will list only leaks happening during normal run-time.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>