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

[receiver/azureeventhub] Fix memory leak on shutdown #32401

Merged
merged 2 commits into from Apr 16, 2024

Conversation

crobert-1
Copy link
Member

Description:

As explained here, components need to cancel all their work and background tasks before returning from Shutdown. My original change for this component to add goleak testing worked around the proper behavior. This PR fully addresses the Shutdown functionality to ensure the component behaves the way the spec requires.

Link to tracking Issue:
#30438

Testing:
Tests are passing.

@djaglowski djaglowski merged commit 62df686 into open-telemetry:main Apr 16, 2024
170 checks passed
@github-actions github-actions bot added this to the next release milestone Apr 16, 2024
rimitchell pushed a commit to rimitchell/opentelemetry-collector-contrib that referenced this pull request May 8, 2024
…32401)

**Description:** <Describe what has changed.>
<!--Ex. Fixing a bug - Describe the bug and how this fixes the issue.
Ex. Adding a feature - Explain what this achieves.-->
As explained
[here](open-telemetry#30438 (comment)),
components need to cancel all their work and background tasks before
returning from `Shutdown`. My original [change for this
component](open-telemetry#32364)
to add `goleak` testing worked around the proper behavior. This PR fully
addresses the `Shutdown` functionality to ensure the component behaves
the way the spec requires.

**Link to tracking Issue:** <Issue number if applicable>
open-telemetry#30438

**Testing:** <Describe what testing was performed and which tests were
added.>
Tests are passing.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants