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.

Lighthouse returned error: INTERNAL: APP::1: Abnormal renderer termination, status = crashed exit_code = 1

See original GitHub issue

Provide the steps to reproduce

Run LH on https://www.sodexoengage.com/

This BUG is reported only from https://developers.google.com/speed/pagespeed/insights/ usign LH in local work as normal

What is the current behavior?

Requested URL: https://www.googleapis.com/pagespeedonline/v5/runPagespeed?key=_KEY__&locale=en_US&url=https%3A%2F%2Fwww.sodexoengage.com%2F&strategy=desktop

Response with:

{
  "error": {
    "code": 500,
    "message": "Lighthouse returned error: INTERNAL: APP::1: Lost browser connection.",
    "errors": [
      {
        "message": "Lighthouse returned error: INTERNAL: APP::1: Lost browser connection.",
        "domain": "lighthouse",
        "reason": "lighthouseError"
      }
    ]
  }
}

What is the expected behavior?

I’m looking for Insight report

Environment Information

Affected Channels: Online service at https://developers.google.com/speed/pagespeed/insights/
Lighthouse version: V5
Chrome version: not applicable
Node.js version: not applicable
Operating System: not applicable

Related issues

Issue Analytics

State:
Created 3 years ago
Comments:5 (1 by maintainers)

Top GitHub Comments

1reaction

chrisdeemingcommented, Aug 3, 2020

We were experiencing the same error when testing any XenForo 2.2 installation although we have worked around the issue for now.

We have ascertained that it appears to be related to this Headless Chromium bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1090429

Specifically our PWA supports the Notification.badge API so when the headless Chromium instance Lighthouse uses encounters that it crashes and returns the internal app error.

0reactions

patrickhulcecommented, May 4, 2020

From #10696 https://sozer.com/ also repros

Top Results From Across the Web

Lighthouse returned error: generic::internal: APP::1 status ...

when running the test I get Details: net::ERR_ACCESS_DENIED. This often happens when you have something like ModSec installed on your server ...

Error: Lighthouse failed with exit code 1 - DNS_FAILURE #42

I can't seem to find my way out of this error: "lighthouseVersion": "8.0.0", ... Error: Lighthouse failed with exit code 1 - DNS_FAILURE...

How to Fix 'Terminated With Exit Code 1' Error - Komodor

Exit Code 1 indicates that a container shut down, either because of an application failure or because the image pointed to an invalid...

Troubleshooting 'terminated with exit code 1' error - ContainIQ

It occurs when the foreground process inside a container stops because of an error. In this article we'll look at some of the...

See raw diff - Hugging Face

diff --git a/vocab.txt b/vocab.txt new file mode 100644--- /dev/null +++ b/vocab.txt @@ -0,0 +1,82000 @@ +[PAD] +[UNK] +[CLS] +[MASK] +[SEP] +! +" +#...