-
Notifications
You must be signed in to change notification settings - Fork 397
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
Persistent Memory leaks reported when using ASan #2056
Comments
I think anything allocated via EDIT: Better would be to replace the bodies of |
Is this pointing out a problem with persistent allocator, per se, or a problem in TypeDictionary and its "managed" types? I suppose the example pasted is just one; but are the others all coming in via TypeDictionary types or through a variety of persistent allocations? |
All seem to be TypeDictionary related.
- Matt
… On Nov 24, 2017, at 12:36 PM, Mark Stoodley ***@***.***> wrote:
Is this pointing out a problem with persistent allocator, per se, or a problem in TypeDictionary and its "managed" types? I suppose the example pasted is just one; but are the others all coming in via TypeDictionary types or through a variety of persistent allocations?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
The problem might be due to the fact though we always call |
I just realized the same as @mgaudet while trying to reduce test memory footprint in context of #6905.
|
The above patch also helps a lot when running tests under QEMU - with patch above applied, (RISC-V) @mstoodle: Obviously, I do not know what I'm doing so the change might be completely bogus but I think is well worth exploring. What's the lifecycle of |
When running the Tril tests compiled with Asan,
comptest
reports a large amount of leaked memory all passing throughjitPersistentAlloc
.One answer is that these leaks may be in some sense false positives because of the persistent alloc story, but it would be good to figure if it's possible to remove them.
The text was updated successfully, but these errors were encountered: