https://bugs.kde.org/show_bug.cgi?id=378293
Darshit Shah <dar...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |INVALID
Status|UNCONFIRMED |RESOLVED
--- Comment #4 from Darshit Shah <dar...@gmail.com> ---
Hi
Sorry for the delayed response. While trying to create a minimum working
example for the bug, I realised that the issue was in how we were using
valgrind and not in valgrind itself. The leak was indeed there, but the
original memory was allocated by a part of the program which wasn't run under
valgrind.
Sorry for the noise!
--
You are receiving this mail because:
You are watching all bug changes.
