Skip to content

fix: Ensure dns-sd is always terminated - #161

Merged
mykola-mokhnach merged 2 commits into
mainfrom
dns-sd
Mar 16, 2026
Merged

fix: Ensure dns-sd is always terminated#161
mykola-mokhnach merged 2 commits into
mainfrom
dns-sd

Conversation

@mykola-mokhnach

@mykola-mokhnach mykola-mokhnach commented Mar 15, 2026

Copy link
Copy Markdown
Collaborator

This fixes possible issue where on exception dns-sd process is still running

initializeBrowsing() creates a long-lived browse dns-sd process (Process A) and stores it in _browseProcess.
It then awaits executeDnsSdCommand(...), which spawns a second dns-sd process (Process B) to wait for “STARTING” or timeout.
On timeout, only Process B is killed (in executeDnsSdCommand’s finally). Process A is never killed.
The error path calls cleanup(), which only clears _browseProcess and does not kill the process, so the browse child keeps the Node process alive.

@mykola-mokhnach
mykola-mokhnach merged commit a12ff10 into main Mar 16, 2026
11 checks passed
@mykola-mokhnach
mykola-mokhnach deleted the dns-sd branch March 16, 2026 06:29
github-actions Bot pushed a commit that referenced this pull request Mar 16, 2026
## [0.34.2](v0.34.1...v0.34.2) (2026-03-16)

### Bug Fixes

* Ensure dns-sd is always terminated ([#161](#161)) ([a12ff10](a12ff10))
@github-actions

Copy link
Copy Markdown

🎉 This PR is included in version 0.34.2 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants