Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"You probably have multiple tabs open" ☂ bug #3024

Open
patrickhulce opened this issue Aug 17, 2017 · 2 comments
Open

"You probably have multiple tabs open" ☂ bug #3024

patrickhulce opened this issue Aug 17, 2017 · 2 comments

Comments

@patrickhulce
Copy link
Collaborator

Within Lighthouse, this error comes from driver.assertNoSameOriginServiceWorkerClients. This is called as the first step in setting up the driver to start loading your page and fetches the list of service workers currently controlling the page to check if it is safe to unregister.

If there are pages other than the current one that are being controlled by the same service worker, we won't be able to unregister the worker to obtain accurate results, and so we prevent the run.

There are a few cases in which this error shows up.

  1. You have more than one tab open to the same origin.
    Workaround: close the other tabs to the origin you have open and re-run the audit.
  2. You have another tab open that has an iframe to the same origin.
    Workaround: close the other tab and re-run the audit. This can be more difficult to detect and is easier to run Lighthouse in a clean profile that has no other tabs open.
    Notes: most commonly a YouTube page since sites frequently embed the YouTube player
  3. The target page has an iframe that is also controlled by the service worker.
    Workaround: use the CLI or Chrome Canary to audit the page.
    Notes: tracked by https://bugs.chromium.org/p/chromium/issues/detail?id=750767, fixed in Chromium 61.0.3163.39
  4. The target page has a link[rel=prerender] element to a page controlled by the same service worker.
    Workaround: use the CLI or wait for the prerender page to die (you can see the currently prerendered page at chrome://net-internals/#prerender)
    Example issue: Fails on page with prerender resource hint. #1335
@paulirish
Copy link
Member

Let's add to help/faq docs, same as #2784 (comment)

@connorjclark
Copy link
Collaborator

We should see if we can remove this check/clearing the service worker data, and instead use signals from installability errors on protocol to check if install will work.

@connorjclark connorjclark added P2 and removed P1.5 labels Aug 16, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants