EPERM error attempting to run example #298

tivac · 2017-08-16T18:31:30Z

Trying to run the following code:

var puppeteer = require("puppeteer");

puppeteer.launch().then(async browser => {
    let page = await browser.newPage();
    await page.goto('https://google.com');
    await page.screenshot({ path: 'screenshot.png' });
    browser.close();
});

I got an error:

Error: EPERM: operation not permitted, unlink 'C:\Users\tivac\Desktop\puppeteer-testing\node_modules\puppeteer\.dev_profile1\CrashpadMetrics-active.pma'

In the course of debugging this set DEBUG=* to try and understand where things were failing, but after doing that it then worked fine. 😕

Does the first-run experience not quite work right in non-DEBUG modes? I'm not sure, but that's what happened for me!

puppeteer@0.9.0
npm@5.3.0
node@8.2.1
Windows 10 Version 1607 (OS Build 14393.1593)

The text was updated successfully, but these errors were encountered:

aslushnikov · 2017-08-16T21:52:01Z

Speculating: you might've accidentally launched the script twice, and two parallel puppeteers tried to run chrome with the same profile folder - .dev_profile1.

We should generate profile folder names randomly so that parallel runs of puppeteer work fine.

tivac · 2017-08-16T22:07:09Z

It's possible! Seems unlikely though as I was launching node via the CLI and not doing anything different beyond originally setting headless : false since I wanted to see the browser. It repro'd every time until setting DEBUG, at which point everything began working perfectly.

builden · 2017-08-17T02:36:10Z

+1

vinaybedre · 2017-08-17T04:54:34Z

Hi,
I freshly used with only puppeteer, but still got the same error. I used the https://github.com/GoogleChrome/puppeteer/#usage first example script.

toolness · 2017-08-17T13:17:10Z

I've been running into this problem as well, though with an even simpler example script that just launches the browser and then immediately tries to close it:

const puppeteer = require('puppeteer');

(async () => {
  console.log("Launching browser.");

  const browser = await puppeteer.launch();

  console.log("Closing browser.");

  browser.close();
})();

I've tried manually deleting the node_modules/puppeteer/.dev_profile1 directory before running this script, and the error still occurs.

As a workaround, I've found that simply calling process.exit(0) when I'm finished works okay--puppeteer seems to be very nice about cleaning up any launched Chromium child processes even in the case of unexpected parent process termination, so that's great!

awayken · 2017-08-18T20:32:10Z

I was seeing this the first couple times I ran the usage demo, but I didn't get it every time. About ten minutes later, I see far more successes than errors running the script. I'm not sure if that helps or not.

webuniverseio · 2017-08-20T14:22:50Z

same problem, windows 10, node v7.10.0, puppeteer 1.0.0. setting DEBUG=* doesn't help, tried running as admin

D:\puppeteer>node index.js
fs.js:1081
  return binding.unlink(pathModule._makeLong(path));
                 ^

Error: EPERM: operation not permitted, unlink 'D:\puppeteer\node_modules\puppeteer\.dev_profile1\CrashpadMetrics-active.pma'
    at Object.fs.unlinkSync (fs.js:1081:18)
    at fixWinEPERMSync (D:\puppeteer\node_modules\rimraf\rimraf.js:210:13)
    at rimrafSync (D:\puppeteer\node_modules\rimraf\rimraf.js:310:28)
    at D:\puppeteer\node_modules\rimraf\rimraf.js:341:5
    at Array.forEach (native)
    at rmkidsSync (D:\puppeteer\node_modules\rimraf\rimraf.js:340:26)
    at rmdirSync (D:\puppeteer\node_modules\rimraf\rimraf.js:333:7)
    at fixWinEPERMSync (D:\puppeteer\node_modules\rimraf\rimraf.js:208:5)
    at rimrafSync (D:\puppeteer\node_modules\rimraf\rimraf.js:310:28)
    at ChildProcess.chromeProcess.on (D:\puppeteer\node_modules\puppeteer\lib\Launcher.js:87:7)

PlanetIrata · 2017-08-22T00:06:56Z

+1

islq · 2017-08-22T05:51:52Z

same problem, windows 10, node v8.4.0, puppeteer 0.9.0

aslushnikov · 2017-08-22T07:33:43Z

Everybody: could you please check if tip-of-tree puppeteer works for you? There have been some changes that might address this.

vsemozhetbyt · 2017-08-22T11:09:35Z

Windows 7 x64, Node .js 8.4.0.
With tip-of-tree puppeteer and example code from README.md, now I consistently get this error:

(node:1040) UnhandledPromiseRejectionWarning:
Unhandled promise rejection (rejection id: 1):
Error: EPERM: operation not permitted,
unlink 'c:\Windows\Temp\puppeteer_dev_profile-dgXrpD\CrashpadMetrics-active.pma'

(node:1040) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated.
In the future, promise rejections that are not handled
will terminate the Node.js process with a non-zero exit code.

Profile folders remain in the c:\Windows\Temp\.

vsemozhetbyt · 2017-08-22T11:11:40Z

Each folder contains 2 files with a lock sign (access for system and admins only):

DevToolsActivePort
CrashpadMetrics-active.pma

awayken · 2017-08-22T13:28:06Z

I didn't have any issues when I installed from latest. Caveat: I used a very different setup than what I had when I posted on this issue. At that time, I was integrating Puppeteer into an existing project, and after I got the error a couple of times, it just stopped erroring for some reason.

However, I wanted to give this update a test. I figured creating a new project was the easiest way to test this. I created a new project. I installed with yarn add puppeteer@latest. I ran an index.js file containing the readme example, and everything worked just fine every time I executed it. So... maybe it's fixed? Like I said, this was a different setup than what I had before, so it's not a terribly scientific experiment.

vsemozhetbyt · 2017-08-22T14:03:35Z

FWIW:

'use strict';

const puppeteer = require('puppeteer');

(async () => {
  const browser = await puppeteer.launch();
  const page = await browser.newPage();

  try { await browser.close(); } catch (err) { console.log(err); }
})();

{ Error: EPERM: operation not permitted,
  unlink 'c:\Windows\Temp\puppeteer_dev_profile-BzkIJu\CrashpadMetrics-active.pma'
    at Object.fs.unlinkSync (fs.js:1067:18)
    at fixWinEPERMSync (...\node_modules\rimraf\rimraf.js:210:13)
    at rimrafSync (...\node_modules\rimraf\rimraf.js:310:28)
    at ...\node_modules\rimraf\rimraf.js:341:5
    at Array.forEach (<anonymous>)
    at rmkidsSync (...\node_modules\rimraf\rimraf.js:340:26)
    at rmdirSync (...\node_modules\rimraf\rimraf.js:333:7)
    at fixWinEPERMSync (...\node_modules\rimraf\rimraf.js:208:5)
    at rimrafSync (...\node_modules\rimraf\rimraf.js:310:28)
    at killChromeAndCleanup (...\node_modules\puppeteer\lib\Launcher.js:103:7)
  errno: -4048,
  code: 'EPERM',
  syscall: 'unlink',
  path: 'c:\\Windows\\Temp\\puppeteer_dev_profile-BzkIJu\\CrashpadMetrics-active.pma' }

opub · 2017-08-22T16:29:11Z

I am getting the same unlink error on CrashpadMetrics-active.pma.

Windows 7 Pro machine with fresh installs of Node 8.4.0 and puppeteer 0.9.0 from yesterday.

vsemozhetbyt · 2017-08-23T19:53:00Z

Seems to be fixed for me (Windows 7 x64) after ac109db

aslushnikov · 2017-08-23T23:12:36Z

Yes, should be fixed now.

lumosmind · 2020-08-18T20:03:05Z

I got same problem with default chromium instillation with puppeteer but I solved by using chrome instead of the chromium

bhanuprakash9980 · 2020-08-20T07:43:58Z

I am using puppeteer to extract data and push it into a db since the data is more i subdivided the data and running multiple instances in different computers but then i am getting the same error. Please help @aslushnikov

winsjos · 2020-08-20T14:37:30Z

+1

caihongxu · 2020-12-17T06:25:01Z

I am closing all the pages before closing browser, but still seeing this issue. Anyone else the same?

felipemmorisson · 2020-12-17T22:24:53Z

i have same problem with multiples open and close chromium, i think it's concurrence

caihongxu · 2020-12-18T05:03:03Z

I ended up fixing it in a somewhat ugly way by doing browser.process().kill('SIGKILL'); instead of await browser.close(); And the issue never happended again. Any drawbacks of this?

rbenzazon · 2020-12-18T16:23:16Z

Yes the drawback is that it's not documented in the api and it's a workaround not a solution. The puppeteer dev team should push a fix. Thanks anyway for the notice :-)

…

On Fri, Dec 18, 2020, 06:03 caihongxu ***@***.***> wrote: I ended up fixing it in a somewhat ugly way by doing browser.process().kill('SIGKILL'); instead of await browser.close(); And the issue never happended again. Any drawbacks of this? — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#298 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACLIE5B26YARSKBV22ZNKATSVLPBJANCNFSM4DXFG7VQ> .

pierreminiggio · 2021-01-07T17:42:44Z

~~Hello guys, just had this error in the latest version, in my case it was because I forgot an "await" before a "browser.close()". So you should close the browser like this :~~

await browser.close()

~~My await was already missing before, but It didn't show any error before I installed my project on another computer. So make sure not to forget your awaits just like me :P~~

EDIT : Nevermind, it happens randomly even after making sure the await is there. And The issue started appearing on other projects that were fine before.

kodelio · 2021-01-08T05:54:03Z

Hello,
Neither closing all pages before closing browser or using browser.process().kill('SIGKILL'); is working for me. The issue occurs randomly.

nick-loginov · 2021-01-12T11:40:31Z

~~Hello guys, just had this error in the latest version, in my case it was because I forgot an "await" before a "browser.close()". So you should close the browser like this :~~
await browser.close()
~~My await was already missing before, but It didn't show any error before I installed my project on another computer. So make sure not to forget your awaits just like me :P~~

EDIT : Nevermind, it happens randomly even after making sure the await is there. And The issue started appearing on other projects that were fine before.

+1

cogitozz · 2021-01-13T01:36:53Z

Hello,
Neither closing all pages before closing browser or using browser.process().kill('SIGKILL'); is working for me. The issue occurs randomly.

+1

caihongxu · 2021-01-30T23:02:31Z

browser.process().kill

Using browser.process().kill() had been working well for me so far (since the last time I posted). Note that in order for this to work you need to remove both browser.close() and page.close() code, otherwise you will still get stuck.

manuel-di-iorio · 2021-02-02T14:26:48Z

Closing all browser pages before invoking close() worked for me (thanks @ CreativeBuilds)

const pages = await browser.pages();
await Promise.all(pages.map(page => page.close()));
await browser.close();

kodelio · 2021-02-02T14:32:01Z

browser.process().kill

Using browser.process().kill() had been working well for me so far (since the last time I posted). Note that in order for this to work you need to remove both browser.close() and page.close() code, otherwise you will still get stuck.

Not working for me :(

KrakerXyz · 2021-02-09T01:04:09Z

I started getting this error on a Windows box but it was after other changes I made trying to get puppeteer to run in a Debian VM. One of the things I had to do for Debian was to add '--no-sandbox', '--disable-setuid-sandbox' arguments. Once I removed those, it started working on Windows again.

I forget the exact reason I had needed to add them to for Debian.

rishabh-pachori-habilelabs · 2021-03-01T06:03:40Z

~~Hello guys, just had this error in the latest version, in my case it was because I forgot an "await" before a "browser.close()". So you should close the browser like this :~~
await browser.close()
~~My await was already missing before, but It didn't show any error before I installed my project on another computer. So make sure not to forget your awaits just like me :P~~
EDIT : Nevermind, it happens randomly even after making sure the await is there. And The issue started appearing on other projects that were fine before.
+1

+1

NotWearingPants · 2021-03-01T19:56:06Z

The workaround isn't working for me, I believe the reproduction of this bug is dependent on how fast the computer is.
This is my repro, gets the EPERM after 1-5 loops:

const puppeteer = require('puppeteer');
const sleep = ms => new Promise(resolve => setTimeout(resolve, ms));
(async () => {
	while (true) {
		console.log('launching');
		const browser = await puppeteer.launch({ headless: false, args: ['--no-sandbox'] });
		console.log('sleeping');
		await sleep(1000);
		console.log('closing pages');
		await Promise.all((await browser.pages()).map(async page => await page.close()));
		console.log('closing');
		await browser.close();
		console.log('sleeping');
		await sleep(1000);
	}
})();

I believe the headless: false, --no-sandbox, closing each page, and also the console.logs, all make the entire thing somehow slower in the right places, and cause the crashpad process to stay alive long enough so that rimrafs timeouts and throws the error (about 600ms).

A possible solution (which is bad but works) is to increase rimrafs maxBusyTries option so that it would retry a bit more, eventually it works. A better solution is to disable the crashpad process - #2778.

kodelio · 2021-03-12T06:51:37Z

The workaround isn't working for me, I believe the reproduction of this bug is dependent on how fast the computer is.
This is my repro, gets the EPERM after 1-5 loops:
const puppeteer = require('puppeteer');
const sleep = ms => new Promise(resolve => setTimeout(resolve, ms));
(async () => {
	while (true) {
		console.log('launching');
		const browser = await puppeteer.launch({ headless: false, args: ['--no-sandbox'] });
		console.log('sleeping');
		await sleep(1000);
		console.log('closing pages');
		await Promise.all((await browser.pages()).map(async page => await page.close()));
		console.log('closing');
		await browser.close();
		console.log('sleeping');
		await sleep(1000);
	}
})();
I believe the headless: false, --no-sandbox, closing each page, and also the console.logs, all make the entire thing somehow slower in the right places, and cause the crashpad process to stay alive long enough so that rimrafs timeouts and throws the error (about 600ms).

A possible solution (which is bad but works) is to increase rimrafs maxBusyTries option so that it would retry a bit more, eventually it works. A better solution is to disable the crashpad process - #2778.

Disabling crashpad is actually not working, so not solving the initial issue

waterss · 2021-03-22T17:40:58Z

Removing "args: ["--no-sandbox"]" from my "jest-puppeteer.config.js" file, module.exports object makes this work on windows 10. My module.exports now looks like:

module.exports = {
launch: {
headless: false,
ignoreHTTPSErrors: true,
defaultViewport: { width: 1600, height: 900 },
// slowMo: 100,
// devtools: true,
},
};

my package.json looks like:

{
"name": "jest-cucumber-puppeteer-testing",
"version": "1.0.0",
"description": "jest cucumber puppeteer testing prototype",
"main": "index.js",
"scripts": {
"test": "env-cmd -f .env jest --runInBand",
"report": "node ./cucumber-report-config.js"
},
"runner": "jest-serial-runner",
"author": "",
"license": "",
"dependencies": {
"@types/expect-puppeteer": "^4.4.3",
"@types/jest-environment-puppeteer": "^4.3.2",
"@types/puppeteer": "^3.0.1",
"cucumber-html-reporter": "^5.2.0",
"dotenv": "^8.2.0",
"env-cmd": "^10.1.0",
"i": "^0.3.6",
"jasmine": "^3.7.0",
"jest-cucumber": "2.0.12",
"jest-puppeteer": "^4.4.0",
"jest-serial-runner": "^1.1.0",
"puppeteer": "^5.5.0",
"yarn": "^1.22.10"
},
"jest": {
"preset": "jest-puppeteer",
"setupFiles": [
"dotenv/config"
],
"testMatch": [
"**/*.steps.js"
],
"reporters": [
"default",
[
"./node_modules/jest-cucumber/dist/src/reporter",
{
"formatter": "json"
}
]
]
}
}

anotherawesomeprojects · 2021-03-30T18:47:40Z

Closing all browser pages before invoking close() worked for me (thanks @ CreativeBuilds)
const pages = await browser.pages();
await Promise.all(pages.map(page => page.close()));
await browser.close();

Still not work for me, I've tried all approach above, but no one work for me :(

fdterr · 2021-04-08T01:39:49Z

I started getting this error on a Windows box but it was after other changes I made trying to get puppeteer to run in a Debian VM. One of the things I had to do for Debian was to add '--no-sandbox', '--disable-setuid-sandbox' arguments. Once I removed those, it started working on Windows again.

I forget the exact reason I had needed to add them to for Debian.

I had the exact same situation and this seems to have worked for me

alamothe · 2021-06-03T02:07:41Z

#6946 is the only real fix short of switching away from Windows.

Fix for: puppeteer#6946, puppeteer#298 etc. (MAJOR PRIORITY) Problem description: WINDOWS ONLY! Any process involving this library would completely crash ungracefully if browser.close() is unable to delete the /temp/ folder, because the promise never gets fulfilled or rejected. Problem tends to happen on slower computers/VMs or environments with limited access to appdata/local folder. Issue can be hard to reproduce in a lot of cases. Solution: fulfill() in catch for removeFolderAsync(this._tempDirectory) Alternative solutions: - SIMPLE, but not ideal: throw(error) instead, remove console.error(error). - HARDER, ideal: add WORKING runtime arguments to disable Crashpad-Metrics.

warsmit · 2021-08-11T11:21:17Z

I use

I have a solution, you have to close the page before closing the browser. Of course if you have more pages open, close all of them.
await page.close(); await browser.close();

Was having an issue with await browser.close() but thanks to @ivangergo3's answer adding a couple lines to close all the pages gets rid of the crash error! 😄
let pages = await browser.pages()
await Promise.all(pages.map(page =>page.close()))
await browser.close()
Edit 12/17/2020

fixed missing parentheses mentioned below

Thank you. This is working for me.
I use metamask extension (dappeteer) for tests. Sometimes tests cannot close wallet request. This workaround help with this issue.

alamothe · 2021-10-09T20:26:39Z

I would like to report that, while this fix works (I prefer resolved vs rejected) and doesn't hang the browser, there is still a lot of instability caused by removing the temporary directory. Our production service on Windows crashes ever so often due to that. Right now the way we patched this is to schedule (setTimeout) deleting temp folder after a minute instead of immediately during close. Will report if this fully resolves the problem.

MahbbRah · 2021-12-28T12:18:41Z

#6341 (comment)

alamothe · 2021-12-30T06:29:23Z

@MahbbRah sadly doesn't work. This is not user profile but crashpad and metrics.

MahbbRah · 2021-12-30T10:01:33Z

@MahbbRah sadly doesn't work. This is not a user profile but a crashpad and metrics.

For me as well it didn't work. the issue is it kept working suddenly got that bug again. But Yes I fixed it for my case it was this issue and this way I solved it.

talles-coder · 2022-01-15T19:50:20Z

Hello, I know it's not the prettiest thing, but I managed to solve this error using the home page that is created when using "puppeteer.launch()" instead of creating a new page,

I changed:

const page = wait browser.newPage();

for:

const pages = await browser.pages();
const firstPage = page[0]

By Cromium's rule, if all tabs/pages are closed it will also close so you don't need to use the command "await browser.close()"
at the end of it all.

aslushnikov self-assigned this Aug 16, 2017

ebidel mentioned this issue Aug 18, 2017

Error: EPERM: operation not permitted, unlink puppeteer\.dev_profile1\CrashpadMetrics-active.pma #356

Closed

pavelfeldman added the host label Aug 18, 2017

vsemozhetbyt mentioned this issue Aug 19, 2017

doc: examples for .waitForSelector() fail #396

Closed

aslushnikov added the bug label Aug 22, 2017

aslushnikov mentioned this issue Aug 23, 2017

Failure to cleanup temp files on Windows machine #450

Closed

JoelEinbinder mentioned this issue Aug 23, 2017

Kill Chrome quickly on Windows #488

Merged

aslushnikov closed this as completed Aug 23, 2017

dsheiko mentioned this issue Dec 10, 2018

Error: spawn EPERM .. lib\Launcher.js:122:40 on Windows #3645

Closed

statm mentioned this issue Jun 17, 2019

a11y-tests: Run a11y tests on all component examples microsoft/fluentui#9479

Merged

2 tasks

Revadike mentioned this issue Jan 30, 2021

Reopen issue #6793

Closed

NotWearingPants mentioned this issue Mar 1, 2021

Cleanup errors in browser.close hang indefinitely #6946

Closed

andresrondon mentioned this issue Jun 18, 2021

fix(browser-runner): reject promise on error #7338

Merged

bdumitru mentioned this issue Jul 2, 2021

FIX: Fulfill promise in removeFolderAsync() - solves EPERM crash while deleting temp folder #7396

Closed

EPERM error attempting to run example #298

EPERM error attempting to run example #298

Comments

tivac commented Aug 16, 2017

aslushnikov commented Aug 16, 2017

tivac commented Aug 16, 2017

builden commented Aug 17, 2017

vinaybedre commented Aug 17, 2017

toolness commented Aug 17, 2017 • edited

awayken commented Aug 18, 2017

webuniverseio commented Aug 20, 2017

PlanetIrata commented Aug 22, 2017

islq commented Aug 22, 2017

aslushnikov commented Aug 22, 2017

vsemozhetbyt commented Aug 22, 2017

vsemozhetbyt commented Aug 22, 2017 • edited

awayken commented Aug 22, 2017

vsemozhetbyt commented Aug 22, 2017 • edited

opub commented Aug 22, 2017

vsemozhetbyt commented Aug 23, 2017 • edited

aslushnikov commented Aug 23, 2017

lumosmind commented Aug 18, 2020

bhanuprakash9980 commented Aug 20, 2020

winsjos commented Aug 20, 2020

caihongxu commented Dec 17, 2020

felipemmorisson commented Dec 17, 2020

caihongxu commented Dec 18, 2020

rbenzazon commented Dec 18, 2020 via email

pierreminiggio commented Jan 7, 2021 • edited

kodelio commented Jan 8, 2021

nick-loginov commented Jan 12, 2021

cogitozz commented Jan 13, 2021

caihongxu commented Jan 30, 2021

manuel-di-iorio commented Feb 2, 2021

kodelio commented Feb 2, 2021

KrakerXyz commented Feb 9, 2021 • edited

rishabh-pachori-habilelabs commented Mar 1, 2021

NotWearingPants commented Mar 1, 2021

kodelio commented Mar 12, 2021

waterss commented Mar 22, 2021

anotherawesomeprojects commented Mar 30, 2021

fdterr commented Apr 8, 2021

alamothe commented Jun 3, 2021

warsmit commented Aug 11, 2021

alamothe commented Oct 9, 2021

MahbbRah commented Dec 28, 2021

alamothe commented Dec 30, 2021

MahbbRah commented Dec 30, 2021

talles-coder commented Jan 15, 2022

toolness commented Aug 17, 2017 •

edited

vsemozhetbyt commented Aug 22, 2017 •

edited

vsemozhetbyt commented Aug 22, 2017 •

edited

vsemozhetbyt commented Aug 23, 2017 •

edited

pierreminiggio commented Jan 7, 2021 •

edited

KrakerXyz commented Feb 9, 2021 •

edited