Error: You probably have multiple tabs open to the same origin. : ( puppeteer + lighthouse )
See original GitHub issueHi,
I understand that the above mentioned issue ( in headline ) is already discussed and resolved here : https://github.com/GoogleChrome/lighthouse/issues/3024
But I am trying to use lighthouse programmatically integrated with puppeteer and here I am encountering this issue Error: You probably have multiple tabs open to the same origin.
.
Please help me on how can I resolved this issue programmatically.
Thank you
Issue Analytics
- State:
- Created 4 years ago
- Comments:8
Top Results From Across the Web
GoogleChrome/lighthouse - Gitter
I was using nodejs v9.11.1 , then i switched to v8.10.0 however I still get that error, slightly different this time. Error: connect...
Read more >Protractor-puppeteer-plugin
Protractor-puppeteer plugin, Protractor, Puppeteer, Lighthouse, NodeJS ... Error: 'Error: You probably have multiple tabs open to the same origin.
Read more >lighthouse - npm
lighthouse -batch-parallel - Run multiple Lighthouse runs in parallel to accelerate the data collecting process, get the result stream (csv, json ...
Read more >Making Better Use of Lighthouse with Puppeteer
Lighthouse analyzes web apps and web pages, collecting modern performance metrics and insights on developer best practices. The metrics you get ...
Read more >Browser instance get killed while running light house ...
Solution: You need to copy the session token or id from the Puppeteer and pass it on to Google Light House when it...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@ankurgpt6719 the content on the page is never retained with Lighthouse at the moment anyhow, we always reload the page.
Glad you got it working! See #1769 if you have input on not requiring the refresh.
I’ll go ahead and close this for now since you got it working, but feel free to reopen if there’s more to add.
@patrickhulce suggested solution is definitely one of the working solution. But this would not meet the case if the data needs to be retained during the LH run ( we lose the content when page is navigated or closed ). Haven’t explored much around the passes in configuration , would this be helpful ?