From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 51473@debbugs.gnu.org
Subject: bug#51473: [PATCH] Enable xwidget scrolling optimizations, and other xwidgets improvements
Date: Sat, 06 Nov 2021 10:06:06 +0800 [thread overview]
Message-ID: <87r1bu6nsh.fsf@yahoo.com> (raw)
In-Reply-To: <87wnlmdtag.fsf@gnus.org> (Lars Ingebrigtsen's message of "Sat, 06 Nov 2021 01:25:27 +0100")
Lars Ingebrigtsen <larsi@gnus.org> writes:
> Po Lu <luangruo@yahoo.com> writes:
>
>> A temporary workaround is to disable sandboxing of the WebKit
>> sub-processes. Would this be acceptable?
>
> Hm... I'd rather not, if possible. But if that's the only non-invasive
> fix possible...
I will try to find some other non-invasive fix.
>> Also, would it be OK to adopt such a change in the release branch?
> If Emacs 28 is segfaulting (and I assume it is, but I've only tried
> Emacs 29) on a lot of newer systems, then I guess we should.
It's not a segfault, but rather some race condition occurring in
WebKitGTK+, which causes it to invoke one of the GLib logging functions
incorrectly, which then raises SIGTRAP.
This crash also happens in Emacs 27, and also GNOME's Yelp viewer.
next prev parent reply other threads:[~2021-11-06 2:06 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87zgqslafe.fsf.ref@yahoo.com>
2021-10-29 4:30 ` bug#51473: [PATCH] Enable xwidget scrolling optimizations, and other xwidgets improvements Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-10-29 13:18 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-04 23:11 ` Lars Ingebrigtsen
2021-11-05 7:20 ` Eli Zaretskii
2021-11-05 7:29 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-05 7:33 ` Lars Ingebrigtsen
2021-11-05 7:47 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-05 13:35 ` Lars Ingebrigtsen
2021-11-05 7:34 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-05 13:10 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-05 13:32 ` Lars Ingebrigtsen
2021-11-05 13:28 ` Lars Ingebrigtsen
2021-11-05 13:40 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-05 13:48 ` Lars Ingebrigtsen
2021-11-06 0:00 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-06 0:22 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-06 0:25 ` Lars Ingebrigtsen
2021-11-06 2:06 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2021-11-06 5:39 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-06 8:58 ` Eli Zaretskii
2021-11-06 10:41 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-06 17:42 ` Lars Ingebrigtsen
2021-11-07 0:41 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-07 0:55 ` Lars Ingebrigtsen
2021-11-07 1:16 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-07 1:04 ` Lars Ingebrigtsen
2021-11-07 1:18 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-07 1:23 ` Lars Ingebrigtsen
2021-11-07 1:26 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-07 1:29 ` Lars Ingebrigtsen
2021-11-07 1:34 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-07 1:39 ` Lars Ingebrigtsen
2021-11-07 1:55 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-07 2:04 ` Lars Ingebrigtsen
2021-11-07 10:09 ` Eli Zaretskii
2021-11-07 12:03 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-07 12:33 ` Eli Zaretskii
2021-11-07 12:40 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-07 12:52 ` Eli Zaretskii
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r1bu6nsh.fsf@yahoo.com \
--to=bug-gnu-emacs@gnu.org \
--cc=51473@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=luangruo@yahoo.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).