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

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

Open
francescobianco opened this issue Apr 6, 2020 · 5 comments
Assignees
Labels
bug needs-investigation P1.5 PSI/LR PageSpeed Insights and Lightrider

Comments

@francescobianco
Copy link

francescobianco commented Apr 6, 2020

Provide the steps to reproduce

  1. 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

Related issues

@connorjclark connorjclark added the PSI/LR PageSpeed Insights and Lightrider label Apr 6, 2020
@connorjclark
Copy link
Collaborator

I delete your API key from your post - that's private.

@exterkamp
Copy link
Member

I can confirm the consistent repro for this.

@patrickhulce
Copy link
Collaborator

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

@chrisdeeming
Copy link

chrisdeeming commented 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.

@paulirish paulirish self-assigned this Sep 14, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug needs-investigation P1.5 PSI/LR PageSpeed Insights and Lightrider
7 participants