What's wrong with this entry?
Anonymous. No account, no email.
What
The HTTP and SOCKS proxy bridge process shutdown routines have been merged into a single generic handler, fixing a subtle race where one bridge could be left dangling.
Details
- The new shared handler
KpK()correctly checksexitCodeandsignalCodebefore sendingSIGTERM(previously onlypidandkilledwere checked). - The
setTimeouthandle is now.unref()'d so it does not prevent the process from exiting if cleanup takes too long. - Log messages now use the bridge type as a variable:
"Sent SIGTERM to HTTP bridge process"/"Sent SIGTERM to SOCKS bridge process"remain the same visible messages.
Evidence
KpK() function (search for "Sent SIGTERM to ${$} bridge process")
Strings lifted out of the shipped bundle, so the claim above can be checked against them.