{"version":"2.1.140","anchor":"bridge-process-management-unified","canonical_anchor":"bridge-process-management-unified","heading":"Bridge Process Management Unified","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.140\/e\/bridge-process-management-unified","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.140","markdown":"### Bridge Process Management Unified\n\n**What**\n\nThe 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.\n\n**Details**\n\n- The new shared handler `KpK()` correctly checks `exitCode` and `signalCode` before sending `SIGTERM` (previously only `pid` and `killed` were checked).\n- The `setTimeout` handle is now `.unref()`'d so it does not prevent the process from exiting if cleanup takes too long.\n- 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.\n\n**Evidence**\n\n`KpK()` function (search for `\"Sent SIGTERM to ${$} bridge process\"`)"}