| Summary: | www-client/chromium-55.0.2883.21 sandbox violations during emerge | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Andreas Steinmetz <ast> |
| Component: | Current packages | Assignee: | Chromium Project <chromium> |
| Status: | RESOLVED NEEDINFO | ||
| Severity: | normal | ||
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
Build Log Excerpt (privacy mangled)
emerge --info output /etc/chromium/default cgroup configuration script |
||
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. |
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"