Crash tests fail with the Chromium sandbox on Linux

オープン
  • 何か問題がありますか？
#44,094 コメント 2 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

@microsoft-playwright-automation がすでに取り組んでいます。

2026年11月13日 から。

  • #44102 @microsoft-playwright-automation による — オープン

評価

難易度
4/5
見積もり時間
3〜5日
初心者へのやさしさ
30/100
issue の種類
バグ
明瞭さ
おおむね明確
活発さ
停滞
技術スタック
github-actions, playwright, typescript
領域
ci-cd, testing, testing-qa

調査の方向性

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.

索引モデルが issue の本文から書いたものです。

説明

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.
主要言語
TypeScript
スター
99.7k
フォーク
6.8k
平均マージ
16時間 10分
マージ済み PR（30日）
301

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

microsoft/playwright のほかの issue

microsoft/playwright の issue をすべて見る

似ている issue

TypeScript の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。