-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Create SafeBoosterHandle and SafeDataSetHandle #4539
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
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
📝 The change to SafeHandle means that the finalizer for
SafeBoosterHandle
will now be invoked at some point if the call toBoosterCreate
succeeds but an exception is thrown later in this constructor (i.e. an exception prevents the caller from being able to useBooster.Dispose()
). Ideally, code which constructs disposable objects should be robust in ensuring created objects are disposed if a failure would prevent those objects from being disposed by the caller. I'm not ready to submit the change to ensure all the callers dispose of objects deterministically on exceptional paths, but I'd like to merge this one in the meantime.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.
Doing a quick scan of the usages of the Booster and Dataset classes, they are always disposed of in the product code (one in a
using
and the other in atry-finally
. The only case I saw where they aren't disposed of is in the tests.machinelearning/test/Microsoft.ML.Tests/TrainerEstimators/TreeEstimators.cs
Line 494 in 8221dac
machinelearning/test/Microsoft.ML.Tests/TrainerEstimators/TreeEstimators.cs
Line 475 in 8221dac
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.
The
Booster
class is disposed if the constructor returns without throwing an exception. However, ifLightGbmInterfaceUtils.Check
throws an exception from the constructor itself, theSafeBoosterHandle
will have been created by the call toBoosterCreate
but never stored in an object that is later disposed. Prior to the use of aSafeHandle
, an instance in this scenario would never be cleaned up. Now it will be cleaned up by the finalizer.