compositor-worker: Ensure that v8 GC works on the compositor thread |
||||
Issue descriptionSince we may have no idle windows, we need to make confirm that v8 won't continually re-post idle gc work and starve other work in the meantime.
,
Jan 24 2017
,
Jun 7 2017
Assigning to Majid to own. This may be a no-op which already works.
,
Jun 7 2017
I feel that this may no longer be an issue once we have a dedicated thread for animation worklets. In particular on a dedicated thread, it seem reasonable for gc work to starve the web page animation tasks if we are under memory pressure and have no idle period. Do we have a different strategy on main thread?
,
Jun 8 2017
So animation worklets will no longer run on the compositor thread? Idle GC on the main thread is meant to reduce the probability of a blocking GC. It feels like a similar strategy would work for animation worklets.
,
Jun 9 2017
> So animation worklets will no longer run on the compositor thread? Correct. We have not made the migration yet but it is the plan ( issue 731727 ).
,
Oct 20 2017
Closing as the plan of record is to move AW to dedicated thread and it is currently in progress here: https://chromium-review.googlesource.com/c/chromium/src/+/630857 |
||||
►
Sign in to add a comment |
||||
Comment 1 by skyos...@chromium.org
, May 5 2016