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

fix QuiescentRegistryListener leak #122

Merged
merged 1 commit into from
Aug 21, 2024

Conversation

pwinckles
Copy link
Contributor

@pwinckles pwinckles commented Jul 29, 2024

QuiescentRegistryListener instances leak because they are never canceled. QuiescentRegistryListener instances are essentially single use, and should be cancaled after they detected monitorable changes. The reason for this is because the embedded runnable calls DynamicMonitoringView.stop() immediately followed by DynamicMonitoringView.start(). This call to DynamicMonitoringView.start() installs a new QuiescentRegistryListener instance.

`QuiescentRegistryListener` instances leak because they are never
canceled. `QuiescentRegistryListener` instances are essentially single
use, and should be cancaled after they detected monitorable changes.
The reason for this is because the embedded runnable calls
`DynamicMonitoringView.stop()` immediately followed by
`DynamicMonitoringView.start()`. This call to
`DynamicMonitoringView.start()` installs a new
`QuiescentRegistryListener` instance.
@pwinckles pwinckles merged commit 2e4298d into performancecopilot:main Aug 21, 2024
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant