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

### FAQ

- [X] Yes, my issue is not about [variability](https://github.com/GoogleChrome/lighthouse/blob/main/docs/variability.md) or [throttling](https://github.com/GoogleChrome/lighthouse/blob/main/docs/throttling.md).
- [X] Yes, my issue is not about a specific accessibility audit (file with [axe-core](https://github.com/dequelabs/axe-core) instead).
- [X] Yes, my issue is not answered by [other FAQs](https://github.com/GoogleChrome/lighthouse#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:
``` html

@media screen and (min-width: 30em){
.a+.d{}
}
@media screen and (max-width: 30em){
.a{}
}

```

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
3. Chrome canary release and latest versions (131.0.6778.86)
4. 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_