Revert #7276, but test garbage collection of ObservableQuery. #7695
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.
The deletion of
observableQuery.options.context
introduced by #7276 was a blunt solution to a hypothetical problem, so I agree with @francisu that it should be reverted if/when it causes anyone any problems: #7276 (comment)Thanks to #7661, we now have a system for programmatically testing garbage collection of discarded objects, so we can actually enforce the expectation that the whole
ObservableQuery
is garbage collected after the last subscriber is removed (which tears down theObservableQuery
and removes it from theQueryManager
).