<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - memory leak with intel i965 mesa when running android container in Ubuntu" href="https://bugs.freedesktop.org/show_bug.cgi?id=104884#c4">Comment # 4</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - 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:78666679@qq.com" title="yanhua <78666679@qq.com>"> yanhua</a> <pre>I found _mesa_glsl_compile_shader is called very frequently. which will eventually call into glsl_type::get_interface_instance() and then glsl_type::glsl_type(). The glsl_type::get_interface_instance() declare a stack variable gls_type() in glsl_type(), has a free ralloc_array, ralloc_strdup call which will call malloc. If the program exit. this memory will released _mesa_destroy_shader_compiler we call _mesa_glsl_release_types(). Since this memory allocated is useless(just be cached). at least for the stacked object. It is better to release it very soon. My program needs to run a long time. Those memory get no chance to be released. And the system memory is exhausted.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>