[Bug 104884] memory leak with intel i965 mesa when running android container in Ubuntu

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Tue Feb 27 09:11:22 UTC 2018


--- Comment #17 from Eero Tamminen <eero.t.tamminen at intel.com> ---
(In reply to Kenneth Graunke from comment #15)
> (In reply to Jiancong from comment #14)
> > Testing with Simon's patch,removing ralloc_strdup, it still be found
> > following possible leaking points.
> That happens when you forget to glXDestroyContext and glXMakeCurrent to NULL
> to unbind it so it can actually get freed.  It's not a driver bug.

(In reply to Jiancong from comment #16)
> Created attachment 137522 [details]
> Patched with previous fix, and rerun the valgrind memcheck.

Please fix the issue pointed out by Kenneth first, and some of the other
application bugs visible in the valgrind output first.  Otherwise it's hard to
say which of those numerous items in your log are relevant.

Alternative, you could kill the valgrind process with a signal that the
application doesn't catch, but Valgrind can catch (e.g. SIGHUP or SIGXCPU could
be such).  That way application cannot mess up the leakage info with bugs it
has in its exit path (which are irrelevant for tracking down run-time leakage).

Note that for tracking down larger leaks, Valgrind Massif output is often more
useful than Valgrind Memcheck output.

You are receiving this mail because:
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-3d-bugs/attachments/20180227/59bc8b59/attachment.html>

More information about the intel-3d-bugs mailing list