https://bugs.kde.org/show_bug.cgi?id=518020
--- Comment #12 from kaminata <[email protected]> --- (In reply to Harald Sitter from comment #11) > Mind that you need to start heaptrack before the leak begins. Doing it after > the memory is already leaked will not produce useful data. Unfortunately, that's not really feasible on my end because the issue occurs randomly and without any clear trigger. The application may run perfectly for five days straight, or the problem may appear after only a couple of hours. Running Heaptrack continuously for 24 hours isn't very practical, and there's no guarantee that the issue will even occur during that period. -- You are receiving this mail because: You are watching all bug changes.
