Created attachment 451568 [details] Build Log Excerpt (privacy mangled) I'm limiting chromium CPU usage by cpuset means via /sys/fs/cgroup/cpuset/chrome. This seems to trigger sandbox access violations during chromium emerge. Temporary fix is to add the following to /etc/sandbox.conf: SANDBOX_WRITE="/sys/fs/cgroup/cpuset/chrome/tasks"
Please can you post the results of 'emerge --info'. Thanks.
Created attachment 451706 [details] emerge --info output
Created attachment 451708 [details] /etc/chromium/default
Cheers.
> I'm limiting chromium CPU usage by cpuset means via /sys/fs/cgroup/cpuset/chrome. Can you elaborate on that? What steps would I need to take to reproduce this?
Created attachment 451758 [details] cgroup configuration script Run the attached cgroup.start script as root to create the cgroup(s). Replace /etc/chromium/default with the attached version. Start chromium, it will be limited to two cores.
This config is a bit too exotic and I cannot reproduce the problem. If you can figure out what it causing gn to open those cgroup files, please share.