https://bugs.freedesktop.org/show_bug.cgi?id=91982
iive ikalvachev@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |ikalvachev@gmail.com
--- Comment #5 from iive ikalvachev@gmail.com --- Created attachment 118258 --> https://bugs.freedesktop.org/attachment.cgi?id=118258&action=edit Valgrind trace of memory leaks in Mesa3D when compiling same shader over and over. R600 Redwood variant.
You need to run valgrind with `--trace-children` to check something else than apitrace itself. :)
I'm attaching log created with the following command:
`valgrind --log-file=mesa.memleak.r600.valgrind.txt --trace-children=yes --leak-check=full --undef-value-errors=no --partial-loads-ok=yes --freelist-vol=200000000 apitrace replay --loop -b bl2469.trace`
I didn't let it die from memory exhaustion, I pressed ESC and exited normally, so the leaks in this log are definitely lost.