https://bugs.kde.org/show_bug.cgi?id=523813
--- Comment #3 from Zamundaaa <[email protected]> --- > If that's right, then just spreading them out is enough: put freed pools in a > queue, and once a frame is > committed, spend about a millisecond emptying the queue. The rest waits for > the > next frame. No extra thread, so the lock question never comes up. The only > cost > is that memory goes back a few hundred ms late. Associating tasks with frames isn't really a thing we can / want to do. -- You are receiving this mail because: You are watching all bug changes.
