[Bug]: CircleCI E2E test workflows intermittently get stuck in Fontconfig error loop

[Gudahtt]

Describe the bug

For the past month or so, we've been seeing that CircleCI E2E test jobs will occasionally get stuck and stay running indefinitely without ever passing. The logs form the job show the error message:

Fontconfig error: Cannot load default config file: No such file: (null)

Expected behavior

Jobs should timeout after a reasonable timeframe if they get stuck, and this specific error should not be occurring.

Screenshots/Recordings

No response

Steps to reproduce

This happens occasionally on E2E test jobs, we don't know of a way to reliably reproduce it.

Error messages or log output

No response

Version

N/A

Build type

None

Browser

Other (please elaborate in the "Additional Context" section)

Operating system

Other (please elaborate in the "Additional Context" section)

Hardware wallet

No response

Additional context

No response

Severity

No response

[desi]

Potential next steps: @Gudahtt will share link on chromium. Update chromium as a first try of a fix. Verify if the "no sandbox" flag is used with Chromium (as this could be related). This might lead to investigating the image more. We will timebox investigation.

[Gudahtt]

Here is an old Chromium bug that seemed similar: https://bugs.chromium.org/p/chromium/issues/detail?id=1010388

[desi]

The other thing @Gudahtt said he was going to try is to update Chrome and chrome driver.

[Gudahtt]

Reopening because Chrome hasn't been updated yet, and because we've found that the FONTCONFIG_PATH solution did not work

[HowardBraham]

@Gudahtt Chrome and Chromedriver automatically get updated to the latest stable version because of #21481

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had recent activity in the last 90 days. It will be closed in 45 days if there is no further activity. The MetaMask team intends on reviewing this issue before close, and removing the stale label if it is still a bug. We welcome new comments on this issue. We do not intend on closing issues if they report bugs that are still reproducible. Thank you for your contributions.