Agis Anastasopoulos

Me too..

This actually https://github.com/GoogleChrome/puppeteer/issues/1936. Not sure we can do something about it right now. Want to take a stab?

@ashfame since the issue is fixed upstream, could you try with the latest puppeteer version?

@Spunkie I like the idea of having an option to exclude/include URLs by a regex. It should be somewhat simple to implement. I'll try to ship it in the first...

> What does `ulimit -a` from within the container show? ``` core file size (blocks, -c) 0 data seg size (kbytes, -d) unlimited scheduling priority (-e) 0 file size (blocks,...

Another important clue I forgot to outline, is that we pin LXCs to specific cores - each container is pinned to two sibling cores. I verified the the the pinning...

> Can you show the `pids.max` value for the `pids` cgroup of the container is running in? All containers have this set to `max`: ``` $ cat /sys/fs/cgroup/pids/lxc/foo*/pids.max | uniq...

Not sure if this is relevant but I also notice the following difference between Buster (where the issue happens) and Stretch (where it does not): `/etc/lxc/default.conf` in Buster: ``` lxc.net.0.type...

Unfortunately didn't do the trick either. I performed the changes and rebooted the instance without any luck. ``` $ cat /etc/security/limits.d/ec2_lxc.conf # See https://linuxcontainers.org/lxd/docs/master/production-setup * soft nofile 1048576 * hard...

Well the machine has 190GB of memory and when all 48 containers are busy, peak used memory is about 150GB, so I'd say it's very unlikely that we're OOMing. Also,...