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

fixes ort memory leak #5517

Closed
wants to merge 1 commit into from

Conversation

michaelgsharp
Copy link
Member

Fixes the ORT memory leak by disposing of the NamedOnnxValues and makes the OnnxRuntimeOutputCacher disposable and adds a finalizer.

@michaelgsharp michaelgsharp requested a review from a team as a code owner December 1, 2020 18:01
@michaelgsharp
Copy link
Member Author

/azp run

@azure-pipelines
Copy link

Azure Pipelines could not run because the pipeline triggers exclude this branch/path.


~OnnxRuntimeOutputCacher()
{
if (_isDisposed)
Copy link
Contributor

Choose a reason for hiding this comment

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

Does it ever hit this code path?

Copy link
Member Author

Choose a reason for hiding this comment

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

The finalizer is hit. I dont think the Dispose call is though. I left it in cause it would be better to switch to a dispose call when we are able to.

Copy link
Member

Choose a reason for hiding this comment

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

We shouldn't be using a finalizer here.

  1. We should ensure OnnxRuntimeOutputCacher instances get disposed properly.
  2. In the cases where Dispose() is never called by the user, and this object is no longer referenced, all the references to the underlying DisposableNamedOnnxValue will be removed as well. If DisposableNamedOnnxValue is holding on to native memory, it should have a finalizer (or more preferrably use a SafeHandle). The managed object that manages the native memory is responsible for ensuring proper clean up.

We shouldn't be using finalizers to dispose managed objects. Finalizers should only be used for managing native resources.

@michaelgsharp
Copy link
Member Author

@eerhardt after syncing with Harish, we are going to go with his approach here. I will be closing this PR.

@harishsk
Copy link
Contributor

harishsk commented Dec 1, 2020

@eerhardt Can you please review #5518 instead? We are going with this approach.

@michaelgsharp michaelgsharp deleted the ort-memory-leak branch March 3, 2021 03:20
@ghost ghost locked as resolved and limited conversation to collaborators Mar 17, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants