Skip to content
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

Disables memory usage assertions #3641

Conversation

rlratzel
Copy link
Contributor

@rlratzel rlratzel commented Jun 6, 2023

This PR disables the assertions intended to check if memory is being allocated and free'd as expected. Recent failures occurring seemingly infrequently have caused suspicion as to whether these are accurately ensuring if memory is free'd or not. Plus, if the tests change to use memory pools, or pytest-xdist which result in GPU sharing, these assertions will also fail.

Instead, this PR adds a variable which can be easily set to enable or disable the assertions. This will make it convenient for testing for memory leaks locally when the developer knows the environment is appropriate for these assertions. We will likely add memory leak checking back in on a case-by-case basis, possibly using different tools, in a future PR.

@rlratzel rlratzel added improvement Improvement / enhancement to an existing function non-breaking Non-breaking change labels Jun 6, 2023
@rlratzel rlratzel added this to the 23.06 milestone Jun 6, 2023
@rlratzel rlratzel requested a review from a team as a code owner June 6, 2023 21:47
@rlratzel rlratzel self-assigned this Jun 6, 2023
Copy link
Member

@alexbarghi-nv alexbarghi-nv left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

@raydouglass raydouglass merged commit aee6181 into rapidsai:branch-23.06 Jun 7, 2023
@rlratzel rlratzel deleted the branch-23.06-disable_mem_leak_asserts branch September 28, 2023 20:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
improvement Improvement / enhancement to an existing function non-breaking Non-breaking change
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants