search

rialto-php / puphpeteer

A Puppeteer bridge for PHP, supporting the entire API.
MIT License
1.34k stars 208 forks source link

What causes idle_timeout? #141

Open zenichanin opened 3 years ago

zenichanin commented 3 years ago

Recently I've been getting a lot more idle_timeout exceeded exceptions, so I want to diagnose and figure out why it is happening.

Is it due to proxies being slower? Is Chromium not responding after a certain time for certain requests? What's the best way to diagnose this issue? I do not want to raise the idle_timeout as it is already set to 300 seconds, so that should be plenty.

stanolacko commented 3 years ago

Sometimes can happends taht tile between two requests for rialto (bridge between php / puphpeteer / rialto / puppeteer). You need to rise timeout. Because it will happends alsways.

mb0000 commented 2 years ago

@zenichanin - probably a bit late, but perhaps of interest to others: In my experience, the idle_timeout is used for when there is no interaction between Puphpeteer and Node JS, but is monitored from the Node JS code. This might happen if your PHP is looping or simply not interacting with Node JS via Puphpeteer. In a sense, it provides a fail safe for Node JS id your PHP process were to crash, such that the Node JS process would shut down after the idle_timeout.