[BUG] Error: EPERM: operation not permitted, unlink "..../CrashpadMetrics-active.pma"

[meotimdihia]

Context:

• Playwright Version: ^v1.6.2
  System:
  OS: Windows 10 10.0.19041
  Memory: 5.71 GB / 15.92 GB
  Binaries:
  Node: 12.14.0 - C:\Program Files\nodejs\node.EXE
  Yarn: 1.22.5 - ~.yarn\bin\yarn.CMD
  npm: 6.14.10 - C:\Program Files\nodejs\npm.CMD
  Languages:
  Bash: 4.4.23 - C:\Program Files\git\usr\bin\bash.EXE

Code Snippet

let browser
;(async () => {
  try {
    const { chromium } = require("playwright")
    browser = await chromium.launch()
    const context = await browser.newContext()
    const page = await context.newPage()
    await page.goto("https://exampsas12le.com")
  } catch (e) {
//    await new Promise(resolve => setTimeout(resolve, 1000))  // The bug won't happen if I uncomment this line
    await browser.close()
  }
})()

Describe the bug
The code works fine in headless: false mode but the bug appear in headless mode.

$ node dist/src/examples/test
[Error: EPERM: operation not permitted, unlink 'C:\Users\meoti\AppData\Local\Temp\playwright_chromiumdev_profile-CVW7lo\CrashpadMetrics-active.pma'] {
  errno: -4048,
  code: 'EPERM',
  syscall: 'unlink',
  path: 'C:\\Users\\meoti\\AppData\\Local\\Temp\\playwright_chromiumdev_profile-CVW7lo\\CrashpadMetrics-active.pma'
}

[JoelEinbinder]

Thanks for the report. Does this happen on any url?

[meotimdihia]

This always happens when did I use: - A dead proxy to fetch data - Or no proxy but fetch a non-existing URL

…

On Tue, Dec 22, 2020 at 00:54 Joel Einbinder ***@***.***> wrote: Thanks for the report. Does this happen on any url? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#4780 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AACJPIIXGTCB7YWAAN5EF33SV6DVZANCNFSM4VC4ZI2Q> .

[pavelfeldman]

@dgozman could it be that you fixed it?

[aslushnikov]

Crash reporter has been disabled in Firefox in #5514. The new version will be released in v1.9.0, and hopefully we won't see this issue ever again