[Heaptrack] [Bug 386435] heaptrack incorrectly reports realloc as leaks

https://bugs.kde.org/show_bug.cgi?id=386435 Andrew Crouthamel changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO

[Heaptrack] [Bug 386435] heaptrack incorrectly reports realloc as leaks

https://bugs.kde.org/show_bug.cgi?id=386435 Andrew Crouthamel changed: What|Removed |Added Keywords||triaged --- Comment #5 from Andrew

[Heaptrack] [Bug 386435] heaptrack incorrectly reports realloc as leaks

https://bugs.kde.org/show_bug.cgi?id=386435 Milian Wolff changed: What|Removed |Added Resolution|--- |WAITINGFORINFO

[Heaptrack] [Bug 386435] heaptrack incorrectly reports realloc as leaks

https://bugs.kde.org/show_bug.cgi?id=386435 --- Comment #3 from Milian Wolff --- yes, it could be a problem in heaptrack - but without a way for me to reproduce this, I will have a hard time tracking it down. And I have zero experience with tor, so what you are writing about it

[Heaptrack] [Bug 386435] heaptrack incorrectly reports realloc as leaks

https://bugs.kde.org/show_bug.cgi?id=386435 --- Comment #2 from Hello71 --- unfortunately, I am unable to reproduce this with a small test case. I suspect it may be a race condition somewhere. if you configure tor as a middle relay and run for an hour, you should see it.

[Heaptrack] [Bug 386435] heaptrack incorrectly reports realloc as leaks

https://bugs.kde.org/show_bug.cgi?id=386435 --- Comment #1 from Milian Wolff --- Can you add an MWE? Some code that shows a leak with heaptrack where there should be none? -- You are receiving this mail because: You are watching all bug changes.