https://bugs.kde.org/show_bug.cgi?id=394627
--- Comment #6 from Milian Wolff <m...@milianw.de> --- ugh, looks like it's an issue when using heaptrack with your custom debug_free/new - can you disable that while using heaptrack for now? I'll have to figure out how to prevent the lock order violation... Probably needs a custom allocator, which I wanted to implement anyways for some time now... -- You are receiving this mail because: You are watching all bug changes.
