-
Notifications
You must be signed in to change notification settings - Fork 12.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Memory Leak #134
Comments
It's entirely possible that you have found a defect but how do you know there's a leak? |
Thanks for the replay. I'm running it in Ubuntu. I am monitoring the process with System Monitor (or |
You are looking at the RSS and it is growing unbounded? Even still this could be a confusing signal. As long as the memory is released before the program exits, it's not a leak. Generally I'd advise that you use LeakSanitizer to check but it's not clear to me whether you could safely do that with sanitizer code itself. Maybe it would be better to discuss what led you to start looking there? |
Yes, I am looking at the Memory field of |
…lineAttr (llvm#134) Setting inline attributes based on user input and command line options. This is optional as functions do not need such an attribute will not get the attribute.
…lineAttr (llvm#134) Setting inline attributes based on user input and command line options. This is optional as functions do not need such an attribute will not get the attribute.
…lineAttr (llvm#134) Setting inline attributes based on user input and command line options. This is optional as functions do not need such an attribute will not get the attribute.
…#134) This patch removes the `LoopWrapperInterface` from `omp.parallel` and updates the semantics of the interface to make loop wrapper restrictions mandatory to operations that have it, rather than a role they might optionally take. MLIR operation verifiers are updated to expect the "hoisted omp.parallel" representation for `distribute parallel do`, to be later implemented in place of a loop wrapper `omp.parallel`.
…lineAttr (llvm#134) Setting inline attributes based on user input and command line options. This is optional as functions do not need such an attribute will not get the attribute.
Hello,
I am calling to the function
__sanitizer_symbolize_pc
several times from my application and it is leaking memory.I have executed also your tests inside an endless loop and they are also leaking memory:
https://github.com/llvm/llvm-project/blob/master/compiler-rt/test/sanitizer_common/TestCases/symbolize_pc.cpp
I also detected
__sanitizer_symbolize_global
. I haven't tested the rest of the API.Is there any other way that I can use to avoid this problem? I need to extract the function and the source file from the PC.
Thanks.
The text was updated successfully, but these errors were encountered: