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

Avoid memory leak warnings from pypdfium2 #1902

Conversation

dagardner-nv
Copy link
Contributor

Description

  • Import pypdfium2 early to ensure the atexit registered by pypdfium2 is invoked after our after_pipeline method is.

Closes #1864

By Submitting this PR I confirm:

  • I am familiar with the Contributing Guidelines.
  • When the PR is ready for review, new or existing tests cover these changes.
  • When the PR is ready for review, the documentation is up to date with these changes.

@dagardner-nv dagardner-nv added bug Something isn't working non-breaking Non-breaking change labels Sep 20, 2024
@dagardner-nv dagardner-nv self-assigned this Sep 20, 2024
@dagardner-nv dagardner-nv requested a review from a team as a code owner September 20, 2024 15:32
@mdemoret-nv
Copy link
Contributor

/merge

@rapids-bot rapids-bot bot merged commit 9a360b2 into nv-morpheus:branch-24.10 Sep 25, 2024
16 checks passed
@dagardner-nv dagardner-nv deleted the david-vdb_upload-pdf-mem-leak branch September 25, 2024 21:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working non-breaking Non-breaking change
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

[BUG]: vdb_upload example produces warnings about a possible memory leak
2 participants