<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_ASSIGNED "
title="ASSIGNED - memory leak with intel i965 mesa when running android container in Ubuntu"
href="https://bugs.freedesktop.org/show_bug.cgi?id=104884#c15">Comment # 15</a>
on <a class="bz_bug_link
bz_status_ASSIGNED "
title="ASSIGNED - memory leak with intel i965 mesa when running android container in Ubuntu"
href="https://bugs.freedesktop.org/show_bug.cgi?id=104884">bug 104884</a>
from <span class="vcard"><a class="email" href="mailto:kenneth@whitecape.org" title="Kenneth Graunke <kenneth@whitecape.org>"> <span class="fn">Kenneth Graunke</span></a>
</span></b>
<pre>(In reply to Jiancong from <a href="show_bug.cgi?id=104884#c14">comment #14</a>)
<span class="quote">> Testing with Simon's patch,removing ralloc_strdup, it still be found
> following possible leaking points.
>
> ==13823== 40,176 bytes in 1 blocks are possibly lost in loss record 907 of
> 915
> ==13823== at 0x4C2DB8F: malloc (in
> /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
> ==13823== by 0x11BA013C: ralloc_size (ralloc.c:121)
> ==13823== by 0x11BA021D: rzalloc_size (ralloc.c:153)
> ==13823== by 0x11BA1331: ra_alloc_reg_set (register_allocate.c:197)
> ==13823== by 0x11EF1EEC: brw_vec4_alloc_reg_set
> (brw_vec4_reg_allocate.cpp:116)
> ==13823== by 0x11E2D128: brw_compiler_create (brw_compiler.c:113)
> ==13823== by 0x11CDD337: intelInitScreen2 (intel_screen.c:2667)
> ==13823== by 0x11C6D1B6: driCreateNewScreen2 (dri_util.c:151)
> ==13823== by 0xFFDDED6: dri3_create_screen (dri3_glx.c:869)
> ==13823== by 0xFFB1CD0: AllocAndFetchScreenConfigs (glxext.c:820)
> ==13823== by 0xFFB1CD0: __glXInitialize (glxext.c:946)
> ==13823== by 0xFFAD811: glXGetFBConfigs (glxcmds.c:1655)
> ==13823== by 0x1CA398E4: (anonymous
> namespace)::GlxDisplay::queryConfigs(int, void (*)(void*, EglOS::ConfigInfo
> const*)</span >
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.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
</ul>
</body>
</html>