Skip to content

Fix message ports not being closed when proxy is relased #678

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

Merged

Conversation

achim-k
Copy link
Contributor

@achim-k achim-k commented Jan 13, 2025

Fixes a regression that was introduced in #653 in that releasing a proxy would not close the underlying message port endpoints. The reason for this was that requestResponseMessage was called with a new Map, causing the returned promise to never settle and preventing closeEndpoint(ep) from being called.

This PR fixes this by making sure that we always pass the endpoint's pending listeners to the requestResponseMessage function. Both the endpoint and its pending listeners are now passed as a single object to all relevant functions to reflect the tight coupling between those.

@ivancuric
Copy link

cc @surma @benjamind

@matthewdavi
Copy link

Would be nice to see this merged. Is there anything blocking it?

@benjamind
Copy link
Collaborator

Mostly that myself and @surma are too busy to look at it. Apologies for that. We need more maintainers for this project!

@benjamind benjamind merged commit 114a4a6 into GoogleChromeLabs:main Jun 18, 2025
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants