[per-agent scheduling] Don't wait for non-ordinary page frame signals.
Frames for non-ordinary pages don't report signals (such as FMP or onload). They also have no parent frame, so they are considered main frames, and they use arbitrary agent cluster IDs. This can create situations where we will "affect" queues forever. The solution is to not add such frames to the "waiting for signal" set. This avoids waiting for them indefinitely, while also not throttling them. The CL also changes it so that we don't try affect queues not associated with a frame (i.e.: have no FrameScheduler), as those are "global" queues that are not associated with a single agent. Bug: 1090251,1115389 Change-Id: I8e624626694aa5aded7bce1ab6243c57eb69ebd7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2352584 Commit-Queue: Tal Pressman <talp@chromium.org> Reviewed-by:Alexander Timin <altimin@chromium.org> Reviewed-by:
Kouhei Ueno <kouhei@chromium.org> Reviewed-by:
Kentaro Hara <haraken@chromium.org> Cr-Commit-Position: refs/heads/master@{#797662}
Showing
Please register or sign in to comment