← Back to microsoft/playwright
microsoft / playwright · Issue No. 41935
478b9f05cbda041ee0280904dc7a6e701591023f
test('repro', async ({ page }) => {
await page.goto(`chrome://extensions`);
});
unsure.
npm run ctest: Call rejects with net::ERR_INVALID_URL, chrome survives.npm run ctest --headed: Sometimes passes, sometimes rejects with page.goto: Target page, context or browser has been closed.. Chrome crashes.
PWTEST_CHANNEL=chromium npm run ctest: Call rejects with Target page, context or browser has been closed, then browser crashes.PWTEST_CHANNEL=chromium npm run ctest --headed: Call passes, then browser crashes.
PWTEST_CHANNEL=chrome npm run ctest: Call rejects with Target page, context or browser has been closed, then browser crashes.PWTEST_CHANNEL=chrome npm run ctest --headed: Sometimes passes, sometimes rejects with `page.goto: Target page, context or browser has been closed. In both cases, chrome crashes afterwards.
PWTEST_CHANNEL=msedge npm run ctest + --headed: Passes.npm run ftest + --headed: Rejects with NS_ERROR_FAILURE.npm run wtest + --headed: Rejects with Protocol error (Playwright.navigate): Navigation cancelled.
No response
Simon's Mac.
Relay reads this issue against the repository's contribution signals: the files it is likely to touch, how the maintainers triage work this size, and what the first contribution would exercise.
The full analysis for this issue is still being assembled. Until then, the description above and the thread on GitHub are the most reliable context.