New comment by git-bruh on void-packages repository

https://github.com/void-linux/void-packages/issues/29105#issuecomment-1077453076

Comment:
> Oh, another person! Can you test if `electron10` also results in a segfault? I haven't had much time to look into it recently, but I have a couple of ideas, let me enumerate some of them for everyone.
> 
>     * I am almost sure this is an issue with the difference between TLS (thread local storage) in musl and glibc. See https://wiki.musl-libc.org/design-concepts.html.
> 
>     * https://www.openwall.com/lists/musl/2021/02/03/1 seems to be related.
> 
>     * To test: `-femulated-tls`: This will slow it down but may fix it.
> 
>     * Also another test, we can see if applying this patch https://www.openwall.com/lists/musl/2021/02/17/3 to musl helps at all (but we wouldn't want that in our musl package until it is merged into upstream).
> 
> 
> It is _not_ a stack-size issue, I am almost completely sure of this, I expanded the stack using pthread and also set a very high default stack size when building.

It was indeed a TID caching related issue, see this [patch](https://gitlab.alpinelinux.org/alpine/aports/-/blob/be2a047681e607a97c6378a3ce070e2a44b61e43/community/chromium/musl-tid-caching.patch) for a hacky fix.

[discussion](https://gitlab.alpinelinux.org/alpine/aports/-/issues/13579#note_224393)
[crbug](https://bugs.chromium.org/p/chromium/issues/detail?id=1309235)