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

Chrome crashes with error status: STATUS_BREAKPOINT during Lighthouse test in timespan mode #16271

Open
3 tasks done
andrei-perasaliak opened this issue Dec 2, 2024 · 1 comment

Comments

@andrei-perasaliak
Copy link

FAQ

URL

https://jsbin.com/zeqohozira/edit?html,output

What happened?

We have a site which we test with Lighthouse in timespan mode. Recently all the tests started to fail with Chrome crashes. Chrome showed error code: STATUS_BREAKPOINT. After some investigation we were able to find the minimal page configuration to reproduce the issue:

<!DOCTYPE html>
<html>
<head>
  <meta charset="utf-8">
  <meta name="viewport" content="initial-scale=1.0" />
  <style>
    @media screen and (min-width: 30em){
        .a+.d{}
    }
    @media screen and (max-width: 30em){
        .a{}
    }
  </style>
</head>
<body>
</body>
</html>

Steps to reproduce:

  1. Open a page with the html above
  2. Lighthouse in Chrome DevTools and set Timespan mode, Mobile device, Performance category
  3. Start Test
  4. Refresh the page.
  5. Chrome crashes with error code: STATUS_BREAKPOINT

So the conditions to reproduce the issue are the following:

  1. Viewport scale 1.0.
  2. Media queries with max and min width and intersected elements
  3. Enhanced selectors, e.g. .a~.b or .a+.b
  4. Viewport should be rerequested after test start. It can be page refresh or js code which accesses viewport meta tag
  5. The test should be started from the new tab to replicate the issue.

What did you expect?

Chrome doesn't crash in Timespan mode.

What have you tried?

  1. Lighthouse versions: 12.2.2, 12.1.0, 10.0.0
  2. Chrome canary release and latest versions (131.0.6778.86)
  3. Checked Chrome debug logs but haven't found anything relevant

How were you running Lighthouse?

Chrome DevTools

Lighthouse Version

v12.2.2

Chrome Version

131.0.6778.86

Node Version

No response

OS

Windows

Relevant log output

No response

@adamraine
Copy link
Member

I can reproduce this, but only on Windows. Definitely a weird bug.

FWIW we recommend using navigation mode to test page navigations like this, however the reasons are unrelated to this bug.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants