| Summary: | heaptrack incorrectly reports realloc as leaks | ||
|---|---|---|---|
| Product: | [Applications] Heaptrack | Reporter: | Hello71 <alex_y_xu> |
| Component: | general | Assignee: | Milian Wolff <mail> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | major | Keywords: | triaged |
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Hello71
2017-11-01 16:56:17 UTC
Can you add an MWE? Some code that shows a leak with heaptrack where there should be none? 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. alternatively, I can attach a small heaptrack profile that shows the problem (but I will have to create it first, my current heaptrack profiles are all huge). I assume that heaptrack has the problem though, since jemalloc reports no leaks. 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 is not really helpful to me. Also, I won't have the time to spent hours on reproducing this with tor, then trying to understand the tor codebase to figure out what is going on. We really need an MWE need a way to reproduce this before something can be done Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |