New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Timeouts with 1.12.2 on cloud function #3944

Open
neelance opened this Issue Feb 7, 2019 · 5 comments

Comments

Projects
None yet
5 participants
@neelance
Copy link

neelance commented Feb 7, 2019

  • Puppeteer version: 1.12.2
  • Platform / OS version: Firebase Cloud Function
  • Node.js version: 8

We are using Puppeteer on a Firebase Cloud Function to automatically render PDFs. I upgraded to Puppeteer 1.12.2 and the cloud function started to run into 60s timeouts as soon as there are multiple concurrent requests. Some additional logging shows that some invocations are even hanging at the very beginning of the function. With 1.11.0 everything is fine. I know that this is not much information for reproducing this issue, but I wanted to make you aware anyways. We're staying with the older version for now. Feel free to close.

@aslushnikov

This comment has been minimized.

Copy link
Contributor

aslushnikov commented Feb 7, 2019

@neelance thanks for letting us know. Any chance you can share more information? Which calls timeout for you? Do you use the bundled chromium instance or a custom one? If custom, than which version?

@neelance

This comment has been minimized.

Copy link
Author

neelance commented Feb 7, 2019

I'm using the bundled chromium with --no-sandbox. It does not seem to be a specific call. I put a log statement at the beginning of the function and sometimes the only logs I got were Function execution started and Function execution took 60002 ms, finished with status: 'timeout', which suggests that the function didn't even start to run. The function was triggered by a change to the Firebase Realtime Database. It's all quite strange and I don't really now how to narrow it down.

@adampasz

This comment has been minimized.

Copy link

adampasz commented Feb 8, 2019

I am having issues with timeouts with Node 8 and 1.12.2 as well.
Sorry, I don't have more info. I haven't had time to debug it deeply.
I rolled back to 1.10.0, which does not seem to get stuck.

@cameronlowry

This comment has been minimized.

Copy link

cameronlowry commented Feb 11, 2019

I'm also getting timeouts when upgrading from 1.11.0 to 1.12.2

@coder-pm

This comment has been minimized.

Copy link

coder-pm commented Feb 20, 2019

Look like issue after bugfix: #609 - page.waitForSelector doesn't work on baidu.com.

After few loads of same page I got timeouts on page.waitForSelector. Also my puppeteer instance freezes on page.click (but only after that few loads). Timeout exception stack trace:

TimeoutError: waiting for selector ".selector" failed: timeout 30000ms exceeded, TimeoutError: waiting for selector ".selector" failed: timeout 30000ms exceeded
    at new WaitTask (project_dir\node_modules\puppeteer\lib\DOMWorld.js:554:28)
    at DOMWorld._waitForSelectorOrXPath (project_dir\node_modules\puppeteer\lib\DOMWorld.js:483:22)
    at DOMWorld.waitForSelector (project_dir\node_modules\puppeteer\lib\DOMWorld.js:437:17)
    at Frame.waitForSelector (project_dir\node_modules\puppeteer\lib\FrameManager.js:606:47)
    at Frame.<anonymous> (project_dir\node_modules\puppeteer\lib\helper.js:109:23)
    at Page.waitForSelector (project_dir\node_modules\puppeteer\lib\Page.js:1079:29)
    at Object.visit (project_dir\dist\scraping\runner.js:115:43)
    at process.internalTickCallback (internal/process/next_tick.js:77:7)

Same code works perfectly fine on v1.11.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment