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.

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

Fix concurrent sparkplug #47461

Closed
wants to merge 5 commits into from
Closed

Conversation

targos
Copy link
Member

@targos targos commented Apr 7, 2023

Original commit message:

    [heap] Cache ForegroundTaskRunner in CollectionBarrier

    The API doesn't allow us to invoke GetForegroundTaskRunner() from
    a background thread. We need to cache the task runner in the ctor
    of CollectionBarrier during heap setup.

    We can't create the CollectionBarrier inside Heap's ctor anymore
    because at that point the TaskRunner might not be set up (e.g. Node).

    Bug: v8:13902
    Change-Id: I814b9dbecb0ded673108bfb7b730e7c9338cf5f5
    Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4403395
    Reviewed-by: Michael Lippautz <mlippautz@chromium.org>
    Commit-Queue: Dominik Inführ <dinfuehr@chromium.org>
    Cr-Commit-Position: refs/heads/main@{#86981}

Refs: v8/v8@8f61b41
Original commit message:

    [heap] Cache GetForegroundTaskRunner in IncrementalMarkingJob

    Our API doesn't allow us to invoke GetForegroundTaskRunner() from
    a background thread. We need to cache the task runner in the ctor
    of IncrementalMarkingJob during heap setup.

    This is necessary because we may start incremental marking from
    background threads.

    Bug: v8:13902
    Change-Id: I938c9bf016e05145f1807c27fd477a7b6c859ca4
    Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4405689
    Commit-Queue: Dominik Inführ <dinfuehr@chromium.org>
    Reviewed-by: Michael Lippautz <mlippautz@chromium.org>
    Cr-Commit-Position: refs/heads/main@{#86983}

Refs: v8/v8@f820e70
@nodejs-github-bot
Copy link
Collaborator

Review requested:

  • @nodejs/gyp
  • @nodejs/v8-update

@targos targos added the request-ci Add this label to start a Jenkins CI on a PR. label Apr 7, 2023
@nodejs-github-bot nodejs-github-bot added lib / src Issues and PRs related to general changes in the lib or src directory. needs-ci PRs that need a full CI run. labels Apr 7, 2023
@targos targos added dont-land-on-v14.x dont-land-on-v18.x PRs that should not land on the v18.x-staging branch and should not be released in v18.x. labels Apr 7, 2023
@github-actions github-actions bot removed the request-ci Add this label to start a Jenkins CI on a PR. label Apr 7, 2023
@nodejs-github-bot
Copy link
Collaborator

@targos targos added the request-ci Add this label to start a Jenkins CI on a PR. label Apr 7, 2023
@github-actions github-actions bot removed the request-ci Add this label to start a Jenkins CI on a PR. label Apr 7, 2023
@nodejs-github-bot
Copy link
Collaborator

CI: https://ci.nodejs.org/job/node-test-pull-request/51040/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dont-land-on-v18.x PRs that should not land on the v18.x-staging branch and should not be released in v18.x. lib / src Issues and PRs related to general changes in the lib or src directory. needs-ci PRs that need a full CI run.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants