Crash tests fail with the Chromium sandbox on Linux

Ouverte
  • Quelque chose ne va pas ?
#44,094 2 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

@microsoft-playwright-automation y travaille déjà.

Depuis le 13/11/2026.

  • #44102 par @microsoft-playwright-automation — ouverte

Évaluation

Difficulté
4/5
Temps estimé
3-5 jours
Accessibilité débutants
30/100
Type d'issue
Bug
Clarté
Plutôt claire
Activité
À l'abandon
Stack technique
github-actions, playwright, typescript
Domaine
ci-cd, testing, testing-qa

Piste de recherche

Start with tests/mcp/crash.spec.ts and the sandbox flags in packages/playwright-core/src/tools/mcp/config.ts; compare the failing MCP tests with the passing CDP crash test in tests/mcp/cli-cdp.spec.ts. Run the crash tests on Linux Chrome with --no-sandbox to test the reported hypothesis, then investigate the renderer crash event and revisit the skips in tests/mcp/crash.spec.ts and tests/library/page-event-crash.spec.ts. Done means the cause is identified and the skips match the condition that requires them.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

agent-triage needs-triage

The page crash event does not arrive when Chrome runs with the Chromium sandbox on Linux. This is an inference from the bot results below. No run has tested Chrome on Linux with only the sandbox changed.

Failing tests

The three tests in tests/mcp/crash.spec.ts fail on the ubuntu-latest - chrome MCP job in every run on main since 12 November (13 of 13 runs).

The crash event never arrives:

1) [chrome] › tests/mcp/crash.spec.ts:31:3 › crash recovery › reports the navigation error, then resets and logs the crash
   Error: Test timeout of 30000ms exceeded
     47 |       expect(log).toContain('Page crashed and was reset to about:blank.');
   > 48 |     }).toPass();

2) [chrome] › tests/mcp/crash.spec.ts:58:3 › crash recovery › lists only one tab
   Test timeout of 30000ms exceeded.
   Error: Not connected

3) [chrome] › tests/mcp/crash.spec.ts:79:3 › crash recovery › marks non-current crashed tab in the tab list
   Test timeout of 30000ms exceeded.
   Error: Not connected

In tests 2 and 3, page.waitForEvent('crash') after page.goto('chrome://crash') does not resolve.

Why the sandbox

On Linux, the MCP server starts --browser=chrome with the sandbox on and --browser=chromium with the sandbox off (config.ts#L235-L242). The library starts all browsers with the sandbox off.

Crash tests on the Linux MCP bots, main, 6 to 13 November:

Test Browser Started by Sandbox Ubuntu 26.04 Ubuntu 24.04
mcp/crash.spec.ts (3 tests) Chrome stable MCP server on 0 of 13 passed skipped
mcp/crash.spec.ts (3 tests) Chromium MCP server off 13 of 13 passed skipped
attach via cdp with a crashed page Chrome stable library off 13 of 13 passed 47 of 47 passed
attach via cdp with a crashed page Chromium library off 13 of 13 passed 48 of 48 passed
  • attach via cdp with a crashed page runs in the same job with the same Chrome stable. It navigates to chrome://crash, waits for the crash event, and passes. Thus the Chrome build is not the cause.
  • That test also passed on Ubuntu 24.04 with Chrome and with Chromium. Thus the Ubuntu version is probably not the cause, and the ubuntu24.04 skip names the wrong condition.
  • Chrome on macOS and Windows passes mcp/crash.spec.ts with the sandbox on. Only Linux has the problem.
Skips to examine again
  • tests/mcp/crash.spec.ts#L22: skip on ubuntu24.04, added in #40617.
  • tests/library/page-event-crash.spec.ts#L40: the same skip for Chromium on ubuntu24.04, added in #40156. The library runs with the sandbox off, so this skip does not agree with the sandbox explanation. It is possibly out of date, or specific to the playwright-x64-ubuntu24-64-core machines.
Next steps
  • Run tests/mcp/crash.spec.ts with --no-sandbox on the Linux Chrome bot to confirm that the sandbox is the cause.
  • Replace the ubuntu24.04 skips with the correct condition.
  • Find why a sandboxed Chrome on Linux does not report the renderer crash. The job reports have no browser output or MCP server output.
Langage dominant
TypeScript
Étoiles
99.7k
Forks
6.8k
Merge moyen
16 h 10 min
PR mergées (30 j)
301

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de microsoft/playwright

Toutes les issues de microsoft/playwright

Issues similaires

Plus d'issues TypeScript

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.