Skip to content
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.

Sign up for GitHub

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

Jump to bottom

worker: handle detached MessagePort from a different context #49150

Merged
merged 1 commit into from
Oct 22, 2023
Merged

worker: handle detached MessagePort from a different context #49150

merged 1 commit into from
Oct 22, 2023

Commits on Aug 29, 2023

  1. worker: handle detached MessagePort from a different context 

    When `worker.moveMessagePortToContext` is used, the async handle
associated with the port, will be triggered more than needed (at least
one more time) and with null data. That can be avoided by simply
checking that the data is present and the port is not detached.

Fixes: nodejs#49075
Signed-off-by: Juan José Arboleda <[email protected]>
    @juanarbol
    juanarbol committed Aug 29, 2023
    Configuration menu
    Copy the full SHA
    4a25555 View commit details
    Browse the repository at this point in the history