You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I'm running panther crawler with chrome client on AWS Lambda.
It starts by cron few times per day and every time on own new instance but randomly it throw few errors on creating client.
Does anyone now where should I look to prevent it?
disconnected: unable to send message to renderer (failed to check if window was closed: disconnected: not connected to DevTools) (Session info: chrome-headless-shell=126.0.6478.112)
session not created from chrome not reachable
The text was updated successfully, but these errors were encountered:
This works for us on bare metal servers. Could you please check if it works for AWS Lambda too?
private function getAvailablePort(): int
{
// When providing '0' as port, the OS picks a random available port
$socket = socket_create_listen(0);
socket_getsockname($socket, $address, $port);
socket_close($socket);
return $port;
}
...
$availablePort = getAvailablePort();
$this->browser = Client::createChromeClient(
options: [
'port' => $availablePort,
],
);
Hi, I'm running panther crawler with chrome client on AWS Lambda.
It starts by cron few times per day and every time on own new instance but randomly it throw few errors on creating client.
Does anyone now where should I look to prevent it?
My arguments for client are simple like below:
errors:
The port 9515 is already in use.
disconnected: unable to send message to renderer (failed to check if window was closed: disconnected: not connected to DevTools) (Session info: chrome-headless-shell=126.0.6478.112)
session not created from chrome not reachable
The text was updated successfully, but these errors were encountered: