Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

How to make sure a tab in background will keep running?

See original GitHub issue

Scenario: I am launching chrome with following flags:

      '--disable-background-timer-throttling',
      '--enable-automation',
      '--disable-renderer-backgrounding',
      '--disable-backgrounding-occluded-windows',
      '--disable-ipc-flooding-protection',

And then utilizing puppeteer to do some operations in a tab in the background while I keep focus on a separate tab.

Expectation: The tasks should happen at normal pace in the background tab Reality: The tasks in the background tab are throttled

Please let me know if there are other details that I can provide. Thanks!

Issue Analytics

State:
Created 4 years ago
Comments:16 (2 by maintainers)

Top GitHub Comments

1reaction

VikramTiwaricommented, May 23, 2020

Sorry for such a delayed response @ecolss.

page.evaluate based click doesn’t work because the events are untrusted. Read more here: https://github.com/puppeteer/puppeteer#q-whats-the-difference-between-a-trusted-and-untrusted-input-event
page.click doesn’t work in backgrounded tabs. This happens because when a tab goes into background, chrome starts to throttle the resources for that tab. This post is old but contains the basic ideas behind it. https://developers.google.com/web/updates/2017/03/background_tabs Note that even with the flag enabled these issues do not go away completely.

Hope these answers are helpful.

1reaction

paulirishcommented, Sep 10, 2019

relevant blog post: https://meowni.ca/posts/metronomes/ & https://metronomes.glitch.me/