Open greggman opened 11 years ago
@greggman Thank you for pointing this out. We are very aware of these problems and had ideas similar to yours.
Just a little bit of background, in case you don’t have full knowledge of the architecture: We are running two tasks, a runner that runs the actual movie code, and a renderer that draws changes to the screen. While the renderer does not signalize its ability to draw, the runner will queue and combine any pending changes and flush them as soon as the renderer is free again.
Example:
What should happen:
CPU usage should go down to 0-2%
What happens instead:
On my mac in both Firefox and Chrome 30-50% of the CPU is being used and my battery is going down even though the tab is not visible.
Two solutions come to mind
I suppose some apps might want to keep running even if offscreen. Maybe you should have to opt into always running if you want that? I'd think the default would be best if it didn't DoS the user's machine