| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
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:
|
Sorry, something went wrong.
Sorry, something went wrong.
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Trying #47450 (comment)
/cc @miladfarca @dinfuehr