From: git-bruh <git-bruh@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: electron{9,10}: broken on musl
Date: Thu, 24 Mar 2022 11:06:24 +0100 [thread overview]
Message-ID: <20220324100624.2Um868CrCpW-Ahxcam4DlORn5TZjrdWaz74o8Bs8_7Y@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-29105@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1452 bytes --]
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)
next prev parent reply other threads:[~2022-03-24 10:06 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-27 22:51 [ISSUE] vscode package broken selfisekai
2021-02-27 23:05 ` Johnnynator
2021-02-27 23:09 ` selfisekai
2021-02-27 23:33 ` electron{9,10}: broken on musl ericonr
2021-02-27 23:33 ` ericonr
2021-02-27 23:42 ` ericonr
2021-02-28 2:01 ` fosslinux
2021-02-28 2:02 ` fosslinux
2021-02-28 3:13 ` selfisekai
2021-02-28 7:41 ` fosslinux
2021-02-28 7:41 ` fosslinux
2021-02-28 13:55 ` selfisekai
2021-03-05 5:46 ` kawaiiamber
2022-03-24 10:06 ` git-bruh [this message]
2022-06-23 2:15 ` github-actions
2022-06-25 6:10 ` fosslinux
2022-06-27 7:22 ` selfisekai
2022-09-28 1:04 ` mjeveritt
2022-09-28 1:05 ` mjeveritt
2022-09-28 1:39 ` [ISSUE] [CLOSED] " q66
2022-09-28 1:39 ` q66
2023-02-08 22:02 ` sistematico
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220324100624.2Um868CrCpW-Ahxcam4DlORn5TZjrdWaz74o8Bs8_7Y@z \
--to=git-bruh@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).