I demand that Alex Deucher may or may not have written... > On Fri, Sep 8, 2017 at 11:41 AM, Darren Salt <devs...@moreofthesa.me.uk> wrote: >> Noticed while playing “Valley”, which was causing some 8MB of leakage per >> second. kmemleak listed many entries looking like this: >> >> unreferenced object 0xffff8802c2951800 (size 1024): >> comm "Xorg", pid 2982, jiffies 4297410155 (age 392.787s) >> hex dump (first 32 bytes): >> 00 50 f9 0c 04 88 ff ff 98 08 00 00 00 00 00 00 .P.............. >> 80 07 00 00 00 00 00 00 58 00 00 00 2c 00 00 00 ........X...,... >> backtrace: >> [<ffffffff810cd4c3>] create_object+0x13c/0x261 >> [<ffffffff815abdc2>] kmemleak_alloc+0x20/0x3c >> [<ffffffff810cad1d>] slab_post_alloc_hook+0x42/0x52 >> [<ffffffff810cb8e0>] kmem_cache_alloc+0x67/0x76 >> [<ffffffff813bbb54>] dc_create_stream_for_sink+0x24/0x1cf [snip]
> Possibly the same issue as this? > https://lists.freedesktop.org/archives/dri-devel/2017-August/150564.html No. I've tested that patch in place of mine, and kmemleak shows the leaks again. The offending patch is a5a159d077be / c4e2a09e8414 “drm/amd/display: Refactor atomic check”: it allocates new_stream but then, in various circumstances, fails to release it. If that allocation goes away then I expect that so can this fix. -- | _ | Darren Salt, using Debian GNU/Linux (and Android) | ( ) | | X | ASCII Ribbon campaign against HTML e-mail | / \ | Force has no place where there is need of skill. _______________________________________________ amd-gfx mailing list amd-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/amd-gfx
