Protocol: [Performance] Fix font request flooding

[ryanthemanuel]

We are seeing issues where fonts flood as a result of various things that are either done by an application or by Cypress.

Chrome has some behavior that triggers reloading of in-memory font assets when global style sheets are updated. This has the effect of triggering all font requests to reload. Even though they are in-memory, this produces a flood of CDP events which backs up proxy correlations and bloats the test replay data being captured.

We can fix this by ensuring that the in memory cache is only used in a given context via the ScopeMemoryCachePerContext feature. This will ensure that the resource is in a local cache and it won't replay the CDP events (https://github.com/chromium/chromium/blob/118.0.5993.117/third_party/blink/renderer/platform/loader/fetch/resource_fetcher.cc#L2650-L2652).

Note that we initially tried to fix this issue via #27860 when we thought it was something that Cypress was inherently doing as part of actionability. This did not resolve the issue as frameworks in the apps themselves can be causing the problem as well. As a result as a part of fixing this, we should undo: #27860

[cypress-bot]

Released in 13.5.0.

This comment thread has been locked. If you are still experiencing this issue after upgrading to
Cypress v13.5.0, please open a new issue.

[ryanthemanuel]

Reopening this since we had to revert the change. More to come on the plan going forward with this.

[ryanthemanuel]

We are fairly sure that this is a chromium bug at this point and there is no way we can globally work around it without causing performance problems elsewhere. I logged: https://bugs.chromium.org/p/chromium/issues/detail?id=1502591 to start the conversation with the chromium team to see if we can get it resolved.

[ryanthemanuel]

If this issue is particularly bad in a project, one potential workaround would be to add --enable-features=ScopeMemoryCachePerContext to the chrome/electron browser launch arguments: https://docs.cypress.io/api/plugins/browser-launch-api#Usage

[Narretz]

We are fairly sure that this is a chromium bug at this point and there is no way we can globally work around it without causing performance problems elsewhere. I logged: https://bugs.chromium.org/p/chromium/issues/detail?id=1502591 to start the conversation with the chromium team to see if we can get it resolved.

So was this fixed in Chrome? The ticket is closed as wontfix: https://bugs.chromium.org/p/chromium/issues/detail?id=1502591 but there's also a commit with a fix.

[ryanthemanuel]

We are fairly sure that this is a chromium bug at this point and there is no way we can globally work around it without causing performance problems elsewhere. I logged: bugs.chromium.org/p/chromium/issues/detail?id=1502591 to start the conversation with the chromium team to see if we can get it resolved.

So was this fixed in Chrome? The ticket is closed as wontfix: bugs.chromium.org/p/chromium/issues/detail?id=1502591 but there's also a commit with a fix.

This was fixed on version 121.0.6157.0 of Chrome. I'm not sure why it got marked as wontfix, but I'll try and see if I can get that corrected.