JavaScript halts in inactive android Chrome tab - Stack Overflow

admin管理员组

文章数量:1343359

I have a tiny webpage that streams music that I can listen to on my phone. The JavaScript on the page sets a timeout that loads the next song and plays it when the first song is over.

While the tab is active, everything works fine. But after the tab goes inactive, the timeouts continue to work for a few minutes, and then as soon as the currently playing song finishes, the next song does not load or play.

I'm assuming this is due to Chrome pausing JavaScript execution for the inactive tab, but I don't want to have to keep my screen on the whole time I'm playing music.

I've debugged the code using the Chrome mobile debugger by setting a timeout to run every 500ms that just shows the current Date. Once the screen goes black, the timeout drops to once every 1000ms, which is expected, but after a few minutes, the timeout stops altogether. But once the tab is active again, all the paused timeouts activate and run.

Chrome changing setInterval/setTimeout to 1000ms is expected and accounted for, but pausing execution pletely makes my whole page stop working.

I've tried trying to keep the tab active be running AJAX requests every so often, but those pause as well. Nothing I've tried keeps the JavaScript running.

Basically, is there a way around this? Is there a way to keep the tab active when the screen is off?

I have a tiny webpage that streams music that I can listen to on my phone. The JavaScript on the page sets a timeout that loads the next song and plays it when the first song is over.

While the tab is active, everything works fine. But after the tab goes inactive, the timeouts continue to work for a few minutes, and then as soon as the currently playing song finishes, the next song does not load or play.

I'm assuming this is due to Chrome pausing JavaScript execution for the inactive tab, but I don't want to have to keep my screen on the whole time I'm playing music.

I've debugged the code using the Chrome mobile debugger by setting a timeout to run every 500ms that just shows the current Date. Once the screen goes black, the timeout drops to once every 1000ms, which is expected, but after a few minutes, the timeout stops altogether. But once the tab is active again, all the paused timeouts activate and run.

Chrome changing setInterval/setTimeout to 1000ms is expected and accounted for, but pausing execution pletely makes my whole page stop working.

I've tried trying to keep the tab active be running AJAX requests every so often, but those pause as well. Nothing I've tried keeps the JavaScript running.

Basically, is there a way around this? Is there a way to keep the tab active when the screen is off?

• javascript
• android
• google-chrome

Share Improve this question Follow asked Feb 27, 2014 at 7:01 BenjamBenjam 5,33633 gold badges3030 silver badges3636 bronze badges 4

• Hey. Did you find any solution for the problem?, I am also facing the same problem – Deepanshu Goyal Commented Jan 28, 2016 at 8:32
• As you can see from the answer below, the only solution is to keep the screen on and the browser window open thereby keeping the tab active. – Benjam Commented Jan 29, 2016 at 20:52
• You can try bg-timer-helper. I'm not sure how it works for all execution types, but it works for setTimeout/setInterval – Alexandr Tovmach Commented Oct 16, 2018 at 0:17
• Have (any) browser vendors documented any info about this "optimisation" for mobile devices? I've have a system which requires the "opener" page to service ajax requests for the active (opened) page but not only is the opener page not sending the requests, but the active tab isn't even getting notifications of an ajax timeout error (except under the unlikely condition that the user "tabs back" to the opener page). I need to know if an iframe on an active tab or a frameset under the active tab stays active or not. – Chris Walsh Commented Jan 4, 2021 at 13:28

Add a ment  | 

1 Answer 1

Sorted by: Reset to default 12

No. For performance and battery life reasons we stop all processing on tabs that are not currently active. The devices that these pages run on are very constrained pared to a desktop device and we need to respect the user.

We do have the option to keep music and audio playing in the background (when your screen is off) but you can't move to the next track like you need.

本文标签： JavaScript halts in inactive android Chrome tabStack Overflow