browser.newPage freezes #1409
Comments
|
I had this same issue but when I had puppeteer download Chrome instead of using my own copy it worked. Give that a try. Wasn't working with my 62.0.3202.94 WIN64 it downloaded 62.0.3264.0 |
|
I'm also troubleshooting this behavior right now, also using Puppeteer 0.13.0, but running on an ARMv7 Raspberry Pi (Model B Pi 2) so I can't use the x86_64 Chromium that comes with Puppeteer. As a workaround I followed these instructions from @jindongh in issue #550 and I can get some things to work, but not browser.newPage(). Edit: To clarify, Puppeteer v0.10.2 with the special chromium install instructions I mentioned above works for me on the Raspberry Pi, I'm just seeing if I can get 0.13.0 to work and this has been where I get stuck. |
|
@sylvainlap this looks like an old version of chrome. What's the version of the chromium you run? |
|
My version is v62. I resolved this issue by using puppeteer v0.10.x. |
|
I think this issue shouldn't be closed, it still exists in new version of puppeteer. |
|
The new version of puppeteer is guaranteed to work with the bundled chromium, no other guarantees are made yet. We'll be forward-compatible with chrome versions once the underlying devtools protocol is brought out of experiment. |
|
@aslushnikov I'm using
So this issue should be opened again as the bug seems to happen on current Puppeteer with its bundled chromium? Any suggested temporary solution at this time? |
|
I installed the latest puppeteer npm package (0.13.0) and it has the same problem with the bundled Chromium. |
|
I installed the latest npm package (1.2.0) and |
|
Same issue, but in my case it's only working with puppeteer v1.4, chromium version downloaded: win64-555668 Edit: Opened an issue: #2538 |
|
@laggingreflex I facing the same issue is there any news? |
|
#2564 |
|
same here on lambda, stops at using latest version puppeteer 1.5.0 with HeadlessChrome/69.0.3452.0 |
|
I'm also seeing this issue consistently when puppeteer's HeadlessChrome version (69.0.3452.0) doesn't match the version of Chrome installed on the Windows 2008 RC2 machine (67.0.3396.99) |
|
I/m facing the same issue with puppeteer 1.6.2 and chrome 69.0.3497.100 |
|
I am facing the same issue with puppeteer 1.9 and chrome 71.0.3563.0 (r594312) on linux. Does anyone have a workaround? |
|
Same issue for me as well... Happens after opening around 1000 pages. Some more informations if it helps. I run Puppeter in an Node application inside of a docker container localy. And when Puppeter get stuck. Chrome on my desktop also stops working (pages crashes at the same time I open them). When I restart the docker container/node application then Chrome on my desktop starts working just fine again. Maybe this is an issue with Chrome and not with Puppeteer itself? |
|
Puppeteer 1.8 and 1.9 tested using bundled chromium. The ws connection is unstable and goes down. "Error: Protocol error (Runtime.callFunctionOn): Target closed." No problem, I just set it up again. However, any browser.newPage promises that were pending are now stuck. |
|
Same issue, using: Puppeteer 1.10.0 I'm trying to run this in CircleCI via a node script |
|
Same issue, using: Puppeteer 1.10.0 |
|
@lukeAnderson2015 @sookinoby2 if the It could be there's no enough memory, or host prohibits spawning child processes. In the latter case, try running with Note: the |
|
hmm, this issue has existed for some time now, without any response at all... @sylvainlap could you perhaps reopen this issue? |
|
@aslushnikov I only open a page once every 3000 ms so it's not an issue with either memory or child processes 😕 |
|
@JohanG2012 feel free to file a new issue, but please include enough details so that we can reproduce it locally. |
Will do as soon as I got time 👍 |
|
I have the same issue trying to run puppeteer in CircleCI and it's clearly due to the new versions of puppeteer because it works like a charm if I lock the version to {
"dependencies": {
"puppeteer": "1.0.0"
}
} |
|
Same issue trying to run Puppeteer 1.2.0 on a Windows Server 2016. |
|
@aslushnikov's suggestion has worked for me. I was able to make it work in a CircleCI environment with: const browser = await puppeteer.launch({
args: ['--single-process']
});I wish the error message was more helpful. I was only getting a timeout message after 8 minutes: |
|
Locking puppeteer version to 1.1.1 solved my Chrome Shell: |
|
Had the same issue with Puppeteer |
|
Yep - 1.11.0 downgrade solved this for me too! |
|
Also experiencing this issue with Edit: I've created a new issue: #4039 |
|
I experienced this all the time and this comment explains how I solved it #1947 (comment) |
|
1.11.0 downgrade saved me too. Running on a raspberry Pi model 3 with raspbian. Only puppeteer-core using chromium. |
|
1.14.0 froze as well, downgrade to 1.11.0 works. |
|
im work fine HeadlessChrome/67.0.3361.0 puppeter 1.11.0 |
|
freezing at 1.14.0, fixed by downgrading to 1.11.0 |
|
Do you people know if any other version than 1.11.0 fix this issue? Considering the vulnerability in 1.11.0, it's not the best idea to use it.. 😞 |
|
I was also seeing this when launching Chrome Canary (Version 78.0.3870.0) via Puppeteer. This used to work for me but I guess Canary has been updated since then. Switching to the bundled Chromium fixed the issue for me |
|
I've confirmed this issue on CircleCI environment with bundled Chrome since 89a5c39 |
|
Same with
|
Hi! Can you add fragment or example of your code? |
const puppeteer = require('puppeteer');
//......
async function xxx() {
log(0)
const browser = await puppeteer.launch({
headless: false // Headless mode fails
});
log(1)
const page = await browser.newPage();
log(2) // Never reaching here if not setting headless to false
await page.goto('https://xxx')
// ......
} |
|
Issue persist with puppeteer@5.2.1 and Chromium (782078) (default downloaded by npm installing puppeteer) my code: "?" is never printed. Is there a new already open issue for this somewhere? |
|
See towry/n#148 |
|
Same probleme |
|
Hit same issue running on linux in docker. Adding
Dockerfile: puppeteer.js const browser = await puppeteer.launch({
args: ['--disable-dev-shm-usage', '--disable-gpu'],
executablePath: 'google-chrome-stable'
}); |
|
|
Adding Chrome Version: Chrome/92.0.4515.159 with puppeteer ^10.2.0 |
|
Had this issue on alpine linux v3.14 and downgrading to alpine linux v3.13 fixed it. Not sure why but I'll look into it. |
|
I removed the launch options:--single-process,it's work.🤡 |
and others
Steps to reproduce
What steps will reproduce the problem?
Here is the code:
The code never reaches the
console.log(page).Here is the logs, with
DEBUG=puppeteer:*The text was updated successfully, but these errors were encountered: