Fix process cleanup timeout causing port binding errors in no-hot-reload mode #51632
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Copilot
AI
changed the title
[WIP] Fix issue with dotnet watch run no-hot-reload
Fix process cleanup timeout causing port binding errors in no-hot-reload mode
Nov 8, 2025
This was referenced Nov 8, 2025
tmat
force-pushed
the
copilot/fix-dotnet-watch-run-issue
branch
from
962a9f9 to
e530eaa
Compare
This was referenced Nov 12, 2025
Open
tmat
force-pushed
the
copilot/fix-dotnet-watch-run-issue
branch
from
e530eaa to
f02c99f
Compare
tmat
force-pushed
the
copilot/fix-dotnet-watch-run-issue
branch
from
f02c99f to
395f612
Compare
Member
|
@DustinCampbell ptal |
DustinCampbell
approved these changes
Dec 4, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Running
dotnet watch run --no-hot-reloadfails with "address already in use" errors after file changes because the process cleanup timeout was set to 0 seconds in no-hot-reload mode, force-killing the dev server before it could release network ports.Fixes #51476