NO_TRACING_STARTED error
See original GitHub issueProvide the steps to reproduce
- Run LH on https://www.telegraaf.nl/nieuws/667381/verpleegkundigen-luiden-noodklok-werkdruk-moet-lager
What is the current behavior?
Caught exception: NO_TRACING_STARTED
errors in the console and no performance or PWA score.
What is the expected behavior?
No errors 😃
Environment Information
- Affected Channels: CLI
- Lighthouse version: 4.0.0-alpha.2-3.2.1
- Node.js version: 10.6.0
- Operating System: Ubuntu 18.10 (4.18.0-13-generic)
Related issues
Issue Analytics
- State:
- Created 5 years ago
- Comments:16 (2 by maintainers)
Top Results From Across the Web
How to Fix Valorant Couldn't Start Error - YouTube
how to fix valorant couldn't start error or Valorant Not Working Crashes When Launching returned 5 error code problem.
Read more >How do i fix this error - Microsoft Community
How do i fix this error. create process failed Error code:0xc1. please assist me as quickly as possible. This thread is locked.
Read more >www.fstribune.com/scripts/form/factcheck.php?g=S29...
No information is available for this page.
Read more >GRM spec fiero ???? - Pennock's Fiero Forum
Bryce: My primary objective is to avoid making the class a check writing class since that IMO would end up destroying the class....
Read more >I just watched that e60 stewart deal - Moto-Related - Vital MX
Basically the link between racial and not racing started about here I ... If you read my later post, I frankly dont have...
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
Thanks @jkneepkens, we’re working on a fix now.
Thank you so much for filing @wildlyinaccurate this is first actually reproducible cases of this error I’ve seen!! 🙏