From: Hoshpak <Hoshpak@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: chromium: add upstream patch to help with segfaults
Date: Sat, 23 May 2020 09:46:30 +0200 [thread overview]
Message-ID: <20200523074630.HLOhGiMQA8URmxjDdKjKKmN-bbBD_NdwCdzB7FjdvRA@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-22215@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 679 bytes --]
There's a merged pull request on the void-packages repository
chromium: add upstream patch to help with segfaults
https://github.com/void-linux/void-packages/pull/22215
Description:
[ci skip]
- Built for x86_64, and x86_64-musl.
- Tested on x86_64.
Currently chromium is sporadically segfaulting. This adds a patch I had
previously skipped when updating to 83.0.4103.61 becaused I didn't think
it applied to us (upstream notes it is for the GCC toolchain, but we use
LLVM).
From initial testing this appears to help eliminate the segfaults... but
I don't have a reliable way to test it (that is, I don't have a precise
series of steps to trigger the segfault).
prev parent reply other threads:[~2020-05-23 7:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-23 2:38 [PR PATCH] " pbui
2020-05-23 7:46 ` Hoshpak [this message]
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=20200523074630.HLOhGiMQA8URmxjDdKjKKmN-bbBD_NdwCdzB7FjdvRA@z \
--to=hoshpak@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).