<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - memory leak in `amdgpu_bo_create()`" href="https://bugs.freedesktop.org/show_bug.cgi?id=109389#c7">Comment # 7</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - memory leak in `amdgpu_bo_create()`" href="https://bugs.freedesktop.org/show_bug.cgi?id=109389">bug 109389</a> from <a class="email" href="mailto:czbd@o2.pl" title="Czcibor Bohusz-Dobosz <czbd@o2.pl>"> Czcibor Bohusz-Dobosz</a> <pre>Created <a href="attachment.cgi?id=145288" name="attach_145288" title="DRM/Radeon glxgears memleak log">attachment 145288</a> <a href="attachment.cgi?id=145288&action=edit" title="DRM/Radeon glxgears memleak log">[details]</a> DRM/Radeon glxgears memleak log Took a while to perform some more tests, and it turns out that running glxgears with amdgpu also leaks memory - launching a hundred of glxgears instances leaks about 400 megabytes, only freed after they are killed and the caches are manually dropped with the command `echo 3 > /proc/sys/vm/drop_caches`. Because glxgears does not need Vulkan support, it had also been possible for me to confirm that the massive persisting leak is definitely caused by the amdgpu driver - attached is a bcc memleak log of glxgears taken with the radeon driver. On a side note, launching vkcube seems to leak memory with the described call at a very similar rate as well.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>