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

[dagardner-nv]

Version

24.10

Which installation method(s) does this occur on?

Source

Describe the bug.

Issue appears limited to instances when a pdf file is parsed.

====Pipeline Complete====
Total time: 11.54 sec
Pipeline runtime: 7.79 sec
-> Cannot close object, library is destroyed. This may cause a memory leak!
-> Cannot close object, library is destroyed. This may cause a memory leak!
-> Cannot close object, library is destroyed. This may cause a memory leak!
-> Cannot close object, library is destroyed. This may cause a memory leak!
-> Cannot close object, library is destroyed. This may cause a memory leak!

Minimum reproducible example

python examples/llm/main.py vdb_upload pipeline --source_type filesystem --file_source="./tests/tests_data/test.pdf"

Relevant log output

Click here to see error details

====Pipeline Complete====

Total time: 11.54 sec

Pipeline runtime: 7.79 sec

-> Cannot close object, library is destroyed. This may cause a memory leak!

-> Cannot close object, library is destroyed. This may cause a memory leak!

-> Cannot close object, library is destroyed. This may cause a memory leak!

-> Cannot close object, library is destroyed. This may cause a memory leak!

-> Cannot close object, library is destroyed. This may cause a memory leak!

Full env printout

Click here to see environment details

[Paste the results of print_env.sh here, it will be hidden by default]

Other/Misc.

No response

Code of Conduct

• I agree to follow Morpheus' Code of Conduct
• I have searched the open bugs and have found no duplicates for this bug report