```
Hmmm this looks like https://bugs.chromium.org/p/chromium/issues/detail?id=1365674#c8 again. I don't know why using clone(CLONE_NEWUSER ...) would return EACCES (which causes the crash). It's not documented to return that error code and I couldn't find anything in 5.19 that would change that.
Glibc doesn't seem to change the error code either.
We have a spike of crashes here recently (unsurprisingly, most of them on this 5.19.0 -1010-nvidia-lowlatency #10-Ubuntu kernel). I would call this an upstream Ubuntu bug for now.
```
Relaying the information from https:/ /bugs.chromium. org/p/chromium/ issues/ detail? id=1459821 as it is not publicly visible:
``` /bugs.chromium. org/p/chromium/ issues/ detail? id=1365674# c8 again. I don't know why using clone(CLONE_NEWUSER ...) would return EACCES (which causes the crash). It's not documented to return that error code and I couldn't find anything in 5.19 that would change that.
Hmmm this looks like https:/
Glibc doesn't seem to change the error code either.
We have a spike of crashes here recently (unsurprisingly, most of them on this 5.19.0 -1010-nvidia- lowlatency #10-Ubuntu kernel). I would call this an upstream Ubuntu bug for now.
```