Skip to content

fix: destroy parent port backend when JS env exits #46496

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

Conversation

trop[bot]
Copy link
Contributor

@trop trop bot commented Apr 4, 2025

Backport of #46437

See that PR for details.

Notes: Fix a potential crash in parentPort.

@trop trop bot requested review from codebytere and a team April 4, 2025 16:03
@trop trop bot added 36-x-y backport This is a backport PR semver/patch backwards-compatible bug fixes labels Apr 4, 2025
@ckerr ckerr merged commit 7be433c into 36-x-y Apr 4, 2025
60 checks passed
@ckerr ckerr deleted the trop/36-x-y-bp-fix-destroy-parent-port-backend-when-js-env-exits-1743782594951 branch April 4, 2025 19:11
@release-clerk
Copy link

release-clerk bot commented Apr 4, 2025

Release Notes Persisted

Fix a potential crash in parentPort.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
36-x-y backport This is a backport PR semver/patch backwards-compatible bug fixes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant