unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Alexander Prähauser via Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Po Lu <luangruo@yahoo.com>
Cc: Eli Zaretskii <eliz@gnu.org>, 69478@debbugs.gnu.org
Subject: bug#69478: 30.0.50; Emacs dies after scrolling in eww
Date: Sun, 03 Mar 2024 15:38:59 +0000	[thread overview]
Message-ID: <87r0grfhqi.fsf@protonmail.com> (raw)
In-Reply-To: <87o7bv3irp.fsf@yahoo.com>

"Po Lu" <luangruo@yahoo.com> writes:

> Eli Zaretskii <eliz@gnu.org> writes:
>
>> Unfortunately, the backtrace still shows the error was processed
>> asynchronously.  I have no idea how this is possible.  Po Lu, did we
>> somehow circumvent the x-synchronize mechanism on the master branch?
>
> No, I cannot explain this, except as a result of some code bypassing
> Xlib to issue CopyArea requests unaffected by Xlib synchronization.
> This suggests that cairo is the culprit, but to be certain, please build
> Emacs `--without-cairo' and test whether that eliminates the crash.

It seems to work! So what now? Should I write them a bug report and use
Emacs without cairo for now? 






  reply	other threads:[~2024-03-03 15:38 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-29 18:27 bug#69478: 30.0.50; Emacs dies after scrolling in eww Alexander Prähauser via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-29 18:33 ` Alexander Prähauser via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-29 19:14 ` Eli Zaretskii
2024-02-29 19:15 ` Eli Zaretskii
2024-02-29 19:55   ` Alexander Prähauser via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-29 20:12     ` Eli Zaretskii
2024-02-29 22:07       ` Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-29 23:07         ` Alexander Prähauser via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-29 23:20           ` Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-29 23:32           ` Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-01  1:52             ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-01  7:12               ` Eli Zaretskii
2024-03-01  8:31                 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-01  1:48   ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-01  7:11     ` Eli Zaretskii
2024-03-01  8:30       ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-01 19:08         ` Alexander Prähauser via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-01 19:29           ` Eli Zaretskii
2024-03-01 20:06             ` Alexander Prähauser via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-02  2:15               ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-02 21:09                 ` Alexander Prähauser via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-03  6:16                   ` Eli Zaretskii
2024-03-03  6:56                     ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-03 15:38                       ` Alexander Prähauser via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2024-03-04  2:09                         ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-14  7:55                           ` Eli Zaretskii
2024-03-14  9:36                             ` Alexander Prähauser via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-21 10:20                             ` Eli Zaretskii
2024-03-21 13:06                               ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors

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=87r0grfhqi.fsf@protonmail.com \
    --to=bug-gnu-emacs@gnu.org \
    --cc=69478@debbugs.gnu.org \
    --cc=ahprae@protonmail.com \
    --cc=eliz@gnu.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).