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
After some time, I usually get 1 of the 2 following errors:
This one is more consistent
[ERROR] WebDriverException: Message: disconnected: Unable to receive message from renderer
(failed to check if window was closed: disconnected: not connected to DevTools)
(Session info: chrome=123.0.6312.122)
Stacktrace:
#0 0x00400077a863 <unknown>
....
This one usually occurs the first time invoke the container after starting it
[ERROR] SessionNotCreatedException: Message: session not created: Chrome failed to start: exited normally
(chrome not reachable)
(The process started from chrome location /opt/chrome/chrome is no longer running, so ChromeDriver is assuming that Chrome has crashed.)
Stacktrace:
#0 0x00400077a863 <unknown>
...
I have set my Docker memory at max (16GB) and I do see the memory hover up to 8GB when running this in docker stats (this is a random snapshot when the "curl" in in progress before the exception/error is thrown:
CONTAINER ID NAME CPU % MEM USAGE / LIMIT MEM % NET I/O BLOCK I/O PIDS
842d00592c18 nervous_cray 333.92% 8.133GiB / 15.61GiB 52.09% 29.5kB / 15.9kB 242MB / 2.79MB 79
The text was updated successfully, but these errors were encountered:
Hello, I am having success with this container on Lambda, but when running/testing locally using the Lambda emulator, I get the chromedriver issue. I am running this in on a Mac M1:
In a single terminal I run the container
In the another terminal I curl to invoke it (as per testing Lambda via emulator):
After some time, I usually get 1 of the 2 following errors:
This one is more consistent
This one usually occurs the first time invoke the container after starting it
This might be related to #235
I have set my Docker memory at max (16GB) and I do see the memory hover up to 8GB when running this in
docker stats
(this is a random snapshot when the "curl" in in progress before the exception/error is thrown:The text was updated successfully, but these errors were encountered: