[BUG] MS Edge Chromium cannot end msedge.exe processes in HEAD mode
See original GitHub issueContext:
-
Playwright Version: tested on versions 1.6.1, 1.3.0 and 1.4.0
-
Operating System: Edition Windows 10 Enterprise Version 20H2 Installed on 8/20/2020 OS build 19042.630 Experience Windows Feature Experience Pack 120.2212.31.0
-
Node.js version: v12.10.0
-
Browser: MS Edge Chromium Version 86.0.622.69
-
Extra: Jest v. 23.6 on Visual Studio Code
Code Snippet
Help us help you! Put down a short code snippet that illustrates your bug and that we can run and debug locally. For example:
import { chromium } from "playwright";
import { getEdgePath } from "edge-paths";
jest.setTimeout(10000);
test("Basic Test", async () => {
const browser = await chromium.launch({
headless: false,
executablePath: getEdgePath()
});
const context = await browser.newContext();
const page = await context.newPage();
await page.goto("https://www.google.com");
await page.close();
await context.close();
await browser.close();
});
Describe the bug If you run this test it will pass but then you will see
console.error node_modules/playwright/lib/server/helper.js:59 [Error: EPERM: operation not permitted, unlink ‘[userpath]\AppData\Local\Temp\playwright_chromiumdev_profile-IAueWz\CrashpadMetrics-active.pma’] { errno: -4048, code: ‘EPERM’, syscall: ‘unlink’, path: ‘[userpath]\AppData\Local\Temp\playwright_chromiumdev_profile-IAueWz\CrashpadMetrics-active.pma’ } This error won’t occur if you run the test in head mode.
And if you open task manager you will see two msedge.exe processes that haven’t ended <-- This issue is specific to Edge browser I believe
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (3 by maintainers)
Top GitHub Comments
After updating Edge Chromium to version 87, I no longer see this issue (even in jest). Please feel free to close this issue. Thanks for your time!
Here is the snippet: