1174049 - Timers should not freeze in background tabs and after display off

Status: RESOLVED INCOMPLETE

(Firefox for Android Graveyard :: General, defect)

Description

[Vitaly Puzrin]

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:38.0) Gecko/20100101 Firefox/38.0
Build ID: 20150511103818

Steps to reproduce:

Use `setInterval` to generate events


Actual results:

Timer events not fired at all in background tabs and after display off (but still fire in web worker).


Expected results:

Timer events should fire, but snapped to 1s, as in chrome for android.

See browsers comparison: https://github.com/nodeca/tabex/issues/5

Comment 1

[Kevin Brosnan [Ex-Mozilla]]

We clamp to 15 min for performance reasons. bug 736602

Mark do we want to alter this at all?

Comment 2

[Mark Finkle (:mfinkle) (use needinfo?)]

(In reply to Kevin Brosnan [:kbrosnan] from comment #1)
> We clamp to 15 min for performance reasons. bug 736602
> 
> Mark do we want to alter this at all?

It will obviously cause more power usage if we lower the clamping threshold.

Comment 3

[Vitaly Puzrin]

Did anyone measured real battery consumption difference? I think, if Chrome is ok with 1s throttling, Firefox should be ok too. Previous ticket seems to be caused by traffic use, but that looks like site issue, and happened > 2 years ago.

As alternative, i could suggest to freeze timer deep only when all tabs go to background. If at least 1 tab is active - then 1s. But that's all after power usage check. May be, that's not a problem now.

Comment 4

[James Willcox (:snorp) ([e-mail]) (he/him)]

I think we'd need a compelling reason to change the behavior. Power consumption is a big concern with partners.

Comment 5

[Vitaly Puzrin]

That become a problem when we shared single websocket connection between tabs. Such notification tcp channels a usually pinged once per 25 sec to be alive. As soon as master goes to background, it stops pinging server (because no timer) and connection is closed.

Comment 6

[miralobontiu]

Hi,

Is this issue still reproducible?

Thanks,

Comment 7

[miralobontiu]

Hello,

Due to the lack of additional info, I'll close this issue as Incomplete.
If the reporter (or anyone else) can provide more information, please feel free to reopen or comment on the issue, and we'll have a thorough look on it.

Thank you!