New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 597006 link

Starred by 4 users
Status: Duplicate
Merged: issue 647870
Owner: ----
Closed: Sep 2016
Cc:
█ junov@chromium.org
█ xlai@chromium.org
skyos...@chromium.org
█ alexclarke@chromium.org
rmcilroy@chromium.org
altimin@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Idle callbacks sometimes stop firing

Project Member Reported by skyos...@chromium.org, Mar 22 2016 
Idle callbacks sometimes stop firing. See https://github.com/catapult-project/catapult/issues/2156.

Comment 1 by skyos...@chromium.org, Apr 4 2016 

My theory is that this is related to the 10s (IIRC) timeout we added for idle tasks. So maybe this is actually working correctly.

Comment 2 by rmcilroy@chromium.org, Apr 5 2016 

Yeah, if the renderer goes into the background we stop idle callbacks after 10 seconds to avoid eating power in the background, that might be what's going on here. It should start back up when you bring the renderer into the foreground and though.

Comment 3 by skyos...@chromium.org, Apr 5 2016

Status: Available (was: Untriaged)
Hmm, the linked github issue sounds like this might be happening in the foreground too, so maybe there's a bug here after all.

Comment 4 by skyos...@chromium.org, May 4 2016

Cc: junov@chromium.org
 Issue 609140  has been merged into this issue.

Comment 5 by skyos...@chromium.org, May 4 2016

Cc: xlai@chromium.org

Comment 6 by paulir...@chromium.org, Sep 17 2016

Mergedinto: 647870
Status: Duplicate (was: Available)
►

Sign in to add a comment