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.

Fatal trace logic error - expected start event, got X

See original GitHub issue

I attached the assets from a LR run that resulted in this error message.

assets.txt

I’d provided the lhr too, but it’s on a remote machine, too big and scp keeps crashing (side note, what???)

Some notes:

could not get this to happen locally, neither via node lighthouse nor a local WRS. Only seems to happen in production LR environments
provided assets was from running against bloomberg.com. @exterkamp has a whole list of of other URLs that it happens on too.
does not happen in prod LR
happens on ~5% of requests in canary LR

Related issues

#7691

Issue Analytics

State:
Created 4 years ago
Reactions:9
Comments:27 (3 by maintainers)

Top GitHub Comments

5reactions

Nikunj1703commented, May 9, 2019

Hi, I am also getting this error when I run the Lighthouse test from the CI. It never happens when I run the test locally. This error appears in the Diagnostics of performance metrics for:

Reduce JavaScript execution time
Minimize main-thread work

Is there a work-around I can put in place?

2reactions

patrickhulcecommented, Jun 23, 2020

We expect this has been fixed by #9785 and #9786. The relative silence since that release went out is reassuring too, so we’ll go ahead and close this out but if anyone runs into this in >=6.0.0 and can provide a trace, we’d love to hear about it 😃