<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <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#c11">Comment # 11</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 <a class="email" href="mailto:lemody@gmail.com" title="Tapani Pälli <lemody@gmail.com>"> Tapani Pälli</a> <pre>(In reply to Simon Hausmann from <a href="show_bug.cgi?id=104884#c10">comment #10</a>) > Created <a href="attachment.cgi?id=137353" name="attach_137353" title="Simple patch that changes glsl_type to manage its own memory">attachment 137353</a> <a href="attachment.cgi?id=137353&action=edit" title="Simple patch that changes glsl_type to manage its own memory">[details]</a> <a href='page.cgi?id=splinter.html&bug=104884&attachment=137353'>[review]</a> [review] > Simple patch that changes glsl_type to manage its own memory > > I've made a patch that attempts to simplify the glsl_type memory management > and as a bonus also gets rid of the global mutex. Is this patch worth > submitting to the list? Cool, yeah it looks like it would work, I guess strdup needs to be util_strdup. I thought about this earlier but I wonder if the reason for having the global context is that there are a *lot* of types so now we will have loads of ralloc contexts .. not sure. Please send to mesa-dev for discussion?</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>