https://bugs.kde.org/show_bug.cgi?id=431746
--- Comment #8 from Milian Wolff <m...@milianw.de> --- I see, interesting. is the shim doing anything special? maybe it's handling of execve/fork is messing up something in heaptrack. anyhow, a proper solution is probably going to mean adding the capability to track child processes somehow. that's a longstanding whish request which I sadly never got around to implement. -- You are receiving this mail because: You are watching all bug changes.
