Deferring use of ExportObject shouldn't lead to error #4515
Conversation
This file contains 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
Introduces a liveness scope specifically for the ExportObjects created when handling a client message, releasing it after all of those objects have been obtained and the ExportObjects are no longer needed. Fixes deephaven#4514
niloc132
added
NoDocumentationNeeded
ReleaseNotesNeeded
devinrsmith
reviewed
Sep 19, 2023
rcaudy
approved these changes
Sep 19, 2023
nbauernfeind
approved these changes
Sep 19, 2023
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Introduces a liveness scope specifically for the ExportObjects created when handling a client message, releasing it after all of those objects have been obtained and the ExportObjects are no longer needed.
Fixes #4514