Skip to content

staticaddr: fix crash in loop-in manager shutdown #942

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 1 commit into from
May 14, 2025

Conversation

starius
Copy link
Collaborator

@starius starius commented May 13, 2025

If the notification manager shuts down, sweepReqs channel is closed and sweepReq object received from it becomes nil, causing panic in handleLoopInSweepReq. Now this is fixed by checking if the channel was closed and if it was shutting down loop-in manager itself.

Pull Request Checklist

  • Update release_notes.md if your PR contains major features, breaking changes or bugfixes

If the notification manager shuts down, sweepReqs channel is closed and sweepReq
object received from it becomes nil, causing panic in handleLoopInSweepReq. Now
this is fixed by checking if the channel was closed and if it was shutting down
loop-in manager itself.
@starius starius requested review from bhandras, sputn1ck and hieblmi May 13, 2025 22:27
@starius starius marked this pull request as ready for review May 14, 2025 02:37
Copy link
Member

@bhandras bhandras left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, thank you!

Copy link
Collaborator

@hieblmi hieblmi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the fix!

@starius starius merged commit 38d7401 into lightninglabs:master May 14, 2025
4 checks passed
@starius starius deleted the sweepReq branch May 14, 2025 15:04
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.

3 participants