<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO - High memory usage in Black Mesa" href="https://bugs.freedesktop.org/show_bug.cgi?id=108946#c8">Comment # 8</a> on <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO - High memory usage in Black Mesa" href="https://bugs.freedesktop.org/show_bug.cgi?id=108946">bug 108946</a> from <a class="email" href="mailto:iive@yahoo.com" title="iive@yahoo.com">iive@yahoo.com</a> <pre>(In reply to Ian Romanick from <a href="show_bug.cgi?id=108946#c6">comment #6</a>) > (I'm quite sure I submitted a similar comment earlier today, but it seems to > have just vanished.) > > I ran the API trace in Valgrind massif memory profiler. As far as I can > tell, the application never calls glDeleteShader. We don't release any of > the memory because the app hasn't told us that we can. In that trace there > is is about 2.6GB (on a 64-bit build of apitrace) of intermediate IR that > could be released by calling glDeleteShader on all the shaders that have > been linked. Do you really need to keep all Intermediate Representations of all shaders? The standard does not deal with internal stuff and IR is just that. I thought that in core context you do not need to recompile them and that there is a method to patch the prologue of the binary in compatibility mode (at least for radeon si).</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>