-
Notifications
You must be signed in to change notification settings - Fork 29.6k
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
Closed
Fix concurrent sparkplug #47461
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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
Review requested:
|
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
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
bot
removed
the
request-ci
Add this label to start a Jenkins CI on a PR.
label
Apr 7, 2023
targos
force-pushed
the
fix-concurrent-sparkplug
branch
from
April 7, 2023 08:07
d61b80d
to
81b1a41
Compare
github-actions
bot
removed
the
request-ci
Add this label to start a Jenkins CI on a PR.
label
Apr 7, 2023
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.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Trying #47450 (comment)
/cc @miladfarca @dinfuehr