On Thu, 23 Sep 2021, 16:20 Michael Hudson-Doyle, <email address hidden>
wrote:
> So I am having a bit of a hard time debugging this. My conclusions so
> far:
>
> 1) it's a real problem
> 2) it's related to the new clone3 syscall
>
> Do electron apps use seccomp by default? It seems code has some way to
> turn this off automagically but if I run code --enable-sandbox it
> reliably crashes. Haven't been able to gdb to the crashing point yet
> though.
>
> --
> You received this bug notification because you are a member of Ubuntu
> Toolchain Hackers, which is subscribed to glibc in Ubuntu.
> https://bugs.launchpad.net/bugs/1944468
>
> Title:
> Electron applications all crash upon launch
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1944468/+subscriptions
>
>
Oh looks like these electron apps were built with a chromium that lacks /chromium. googlesource. com/chromium/ src/+/218438259 dd795456f0a48f6 7cbe5b4e520db88 b
this commit
https:/
- which was only 4 months ago. And Chromium's sandbox defaults to crashing
on unknown syscalls. So I guess we're back to the "do we disable clone3 for
impish" question.
On Thu, 23 Sep 2021, 16:20 Michael Hudson-Doyle, <email address hidden>
wrote:
> So I am having a bit of a hard time debugging this. My conclusions so /bugs.launchpad .net/bugs/ 1944468 /bugs.launchpad .net/ubuntu/ +source/ glibc/+ bug/1944468/ +subscriptions
> far:
>
> 1) it's a real problem
> 2) it's related to the new clone3 syscall
>
> Do electron apps use seccomp by default? It seems code has some way to
> turn this off automagically but if I run code --enable-sandbox it
> reliably crashes. Haven't been able to gdb to the crashing point yet
> though.
>
> --
> You received this bug notification because you are a member of Ubuntu
> Toolchain Hackers, which is subscribed to glibc in Ubuntu.
> https:/
>
> Title:
> Electron applications all crash upon launch
>
> To manage notifications about this bug go to:
> https:/
>
>