Open simon-buxton-kg opened 6 years ago
These Firefox and Chrome bugs go into more detail about the problem:
https://bugs.chromium.org/p/chromium/issues/detail?id=519952
You can disable using /dev/shm by passing --disable-dev-shm-usage option when you run Chrome.
https://bugs.chromium.org/p/chromium/issues/detail?id=736452
Is there an equivalent for Firefox?
No, Firefox doesn't offer such a flag based on their documentation: https://developer.mozilla.org/en-US/docs/Mozilla/Command_Line_Options#How_to_use_command_options
--disable-dev-shm-usage
Fixed it for me! Thank you!
In order to avoid random crashes it seems the Firefox and Chrome images need increased shared memory when running in a container, as per:
from https://github.com/SeleniumHQ/docker-selenium#running-the-images
However at the moment AWS Fargate doesn't support this:
from https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task_definition_parameters.html#container_definition_linuxparameters
Just wondering if anyone is actually seeing this problem when trying to use Fargate to run Selenium nodes?