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

Issue 648084 link

Starred by 5 users

Issue metadata

Status: Duplicate
Merged: issue 647484
Owner: ----
Closed: Sep 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows , Mac
Pri: 1
Type: Bug



Sign in to add a comment

Timers stop firing after a while

Project Member Reported by sdy@chromium.org, Sep 18 2016

Issue description

Version: 55.0.2864.0 (Canary)
OS: Tested on macOS 10.11 and 10.12.

What steps will reproduce the problem?
(1) Visit Google Play Music
(2) Play some music
(3) Wait

What is the expected output?
The music keeps playing

What do you see instead?
The music stops playing mid-song after a while, and then if I reload in the same tab I end up at a plain grey page (as if the root page loaded fine, but JS-loaded resources aren't appearing).

I've also seen weirdness in other Google sites — for example, Keep won't load my data, or won't load past the first screenful.
 
play_music_session_ending_in_failure.json
6.2 MB View Download
play_music_reload_in_broken_state.json
1.5 MB View Download

Comment 1 by sdy@chromium.org, Sep 18 2016

(I'll try a bisect, but it takes a little while to reproduce.)

Comment 2 by sdy@chromium.org, Sep 18 2016

Components: -Internals>Network Blink>JavaScript
Summary: Timers stop firing after a while (was: Google sites stop working properly after a while)
Okay, this is interesting. I noticed that if I try to close the tab (which triggers an onbeforeunload popup), and then choose to stay on the tab, the music continues for a few seconds.

If I call setTimeout(() => { console.log('timed out'); }, 100) in the console, the timer doesn't fire unless I go through the onbeforeunload dance. It started happening after ~15 minutes.

The state persists on reload, I have to make a new tab to fix it. Anyway, I don't think this is networking-related anymore.

Bisecting failed, I bet this is a field trial.

Comment 3 by rra...@gmail.com, Sep 19 2016

I'm having the same issue, any info I can provide?
I'm on Windows 10.
Components: Blink>DOM
Labels: Needs-Bisect
Status: Available (was: Untriaged)
Can you reproduce it with --enable-benchmarking too? This should disable all field trials.

Cc: hablich@chromium.org

Comment 6 by sdy@chromium.org, Sep 20 2016

Cc: shrike@chromium.org
Labels: ReleaseBlock-Beta

Comment 7 by shrike@chromium.org, Sep 20 2016

Labels: -ReleaseBlock-Stable OS-Mac OS-Windows
I think this is reported in  Issue 648147 . The conversation there relates to networking - I don't want to duplicate this bug into  Issue 648147  if it turns out the problem is really about timers.

sdy@ - would you please see if disabling field trials makes the problem go away?

Comment 8 Deleted

Comment 9 by ajha@chromium.org, Sep 20 2016

 Issue 647484  looks to be similar and suspected CL has been reverted here https://codereview.chromium.org/2353473003. The revert if related would be available in next canary(>55.0.2865.0) for verification.

Comment 10 by ajha@chromium.org, Sep 20 2016

Cc: ajha@chromium.org
Labels: TE-NeedsTriageFromMTV
Google Play music is not available in India to check and verify the reverted CL on the latest canary(55.0.2866.0).

However the scenario of  Issue 647484  seems to be working fine on the latest canary(55.0.2866.0) on Windows-10, Mac OS 10.11.6 and Linux Ubuntu 14.04.

Looping MTV team@ to verify this scenario as well.
 Issue 648093  has been merged into this issue.

Comment 12 by rra...@gmail.com, Sep 20 2016

I'm not having anymore issues with affected sites with the 55.0.2866.0 update.

Comment 13 by sdy@chromium.org, Sep 20 2016

Mergedinto: 647484
Status: Duplicate (was: Available)
Same here! It looks like this was resolved with the revert mentioned in  issue 647484 .

Sign in to add a comment