CHROME_INTERSTITIAL_ERROR throws on iframes

[benschwarz]

Provide the steps to reproduce

1. Run LH on https://lh-iframe-interstitial.glitch.me/

What is the current behavior?

Lighthouse throws CHROME_INTERSTITIAL_ERROR

What is the expected behavior?

A successful test

Environment Information

• Affected Channels: All
• Lighthouse version: 5.2.0 (works in 5.1.0)
• Node.js version: 11.15.0
• Operating System: Mac OSX, Linux

I ran lighthouse with ndb to get a deeper look in:

In gather-runner.js, #getInterstitialError:

const interstitialRequest = networkRecords.find(record => record.documentURL.startsWith('chrome-error://'))

Returns a single network record, which appears to be a base64 encoded image of the chrome dino error states.

[patrickhulce]

Thanks @benschwarz! I'm not able to reproduce this locally or with PSI though. Do you know if this page is employing geo-based content differentiation?

[benschwarz]

@patrickhulce Not sure about geo-based content differentiation, but I did notice that we did not see the interstitial error when adblocking was turned on.

I think there's an ad/third party somewhere in there that throws one of the chrome-errors that's then identified in the network records. Does that sound plausible?

[benschwarz]

I was able to reproduce this every time. I could share the trace information from --gather-mode if that's useful for re-pro?

[patrickhulce]

No worries I made my own :) https://lh-iframe-interstitial.glitch.me/