-
Notifications
You must be signed in to change notification settings - Fork 74k
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
Fix memory leaks in xla::BufferDonationTest #59033
Fix memory leaks in xla::BufferDonationTest #59033
Conversation
Please wait for code owners approval.
…On Sat, Dec 31, 2022 at 5:53 PM Mihai Maruseac ***@***.***> wrote:
***@***.**** approved this pull request.
—
Reply to this email directly, view it on GitHub
<#59033 (review)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AACVGH3J6NIDKXOF3GLEIS3WQBXJ5ANCNFSM6AAAAAATLL3UWI>
.
You are receiving this because your review was requested.Message ID:
***@***.***>
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
(please wait for review from code owners, sorry for the first approval)
Not my place to review this, should have steered clear of XLA. Sorry
Could you post a leak description and a stacktrace? I'm having a somewhat hard time connecting the code changes to a leak, and we do run tests (at least internally) under asan - perhaps we have missed something? |
Sure, the summary from asan is SUMMARY: AddressSanitizer: 40 byte(s) leaked in 7 allocation(s). That goes from 3 tests, first one is There's 3 buffers in Buffer 16 is not aliased, buffers 4 are aliased. Donation is not specified for this test. In the end, inside For buffers with the size 4, as they're aliased but not donated, it involves making copy buffers in Stacktrace for this case: Direct leak of 24 byte(s) in 3 object(s) allocated from: |
Second test is There's 2 buffers, 4 bytes each, both are leaked. For this test failure is expected, so the buffers are not deallocated when Stacktrace: Direct leak of 8 byte(s) in 2 object(s) allocated from: |
And the third one is There's 3 buffers, 16, 4 and 4 bytes. Buffer 16 is not aliased, buffers 4 are aliased. Donation is specified for this test. Originally only buffers with the size 4 are leaked. It's the same as for the first test - they're in Stacktrace: Direct leak of 8 byte(s) in 2 object(s) allocated from: |
And the last change |
@reedwm Could you take a look? |
Could we remove it from this PR then? Overall the PR looks way too large for something addressing a leak inside a test. |
337a4ab
to
66d21f5
Compare
Sure, this change's been reverted |
Hi @cheshire Can you please review this PR ? Thank you! |
2 similar comments
Hi @cheshire Can you please review this PR ? Thank you! |
Hi @cheshire Can you please review this PR ? Thank you! |
Hi @rbaranchuk-capgemini Can you please resolve conflicts? Thank you! |
This PR is stale because it has been open for 14 days with no activity. It will be closed if no further activity occurs. Thank you. |
Hi @rbaranchuk-capgemini Any update on this PR? Please. Thank you! |
Hi, I'm afraid I have to say at this point I don't even remember what this PR was about when I opened it. And most likely the code been changed since then to the extent that this PR hardly could have any relevance now. So I'm just gonna close it. |
Leaks were detected by AddressSanitizer