New comment by ohoes on void-packages repository

https://github.com/void-linux/void-packages/issues/29654#issuecomment-1879172442

Comment:
> Its not that simple, `--no-sandbox` has a bunch of implications other than the simple filtering of system calls, the issues are most likely related to multi threading and locks/mutexes, `--no-sandbox` makes chromium basically single threaded.

Still, running without sandbox is the only workaround (that I know of), though. Perhaps it would be useful to add it to the package. Without that argument, Chromium is practically unusable on musl.