From: chad <yandros@gmail.com>
To: EMACS development team <emacs-devel@gnu.org>
Subject: Possible issue with pgtk branch
Date: Thu, 14 Jan 2021 16:55:45 -0800 [thread overview]
Message-ID: <CAO2hHWZbdc2=c0SNw8mi1+WOuUP5e_N0wzXV3i8Vfz27+NQ6dg@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1355 bytes --]
I've been trying out the feature/pgtk branch for a while, and I've run into
a mysterious shutdown (not crash) that I haven't been able to isolate yet.
I'm wondering if anyone else is seeing something similar, so I can gather
enough data to file a big report.
I'm running emacs in daemon mode, with at least 2 frames. The shutdown
happens in eww buffers, when I'm scrolling, and perhaps always (at least a
couple times) when I'm scrolling up with M-v. Perhaps relevant, I often use
eww to make web pages more readable, and this often involves me making the
buffer writable (C-x C-q) and removing (killing, ala C-k and C-w)
extraneous junk, which includes images and styled text in various sizes and
perhaps fonts.
This isn't reliable enough for me to catch it under gdb, but I'm trying.
Has anyone else seen anything like this, or perhaps the above behavior
description is enough to suggest something I might do to tickle the issue?
Thanks in advance,
~Chad
P.S. My environment is pretty weird; I'm running emacs inside Crostini, a
debian container running on a lightweight vm inside ChromeOS. This system
uses a wayland-based display engine with a chromeos-custom compositor with
X11 support, described in some detail here:
https://chromium.googlesource.com/chromiumos/platform2/+/413a646b5b7067a989bab2ef9fca0c3a4515cc22/vm_tools/sommelier/README.md
[-- Attachment #2: Type: text/html, Size: 1670 bytes --]
next reply other threads:[~2021-01-15 0:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-15 0:55 chad [this message]
2021-01-15 7:08 ` Possible issue with pgtk branch Eli Zaretskii
2021-01-15 17:49 ` chad
2021-01-15 18:31 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAO2hHWZbdc2=c0SNw8mi1+WOuUP5e_N0wzXV3i8Vfz27+NQ6dg@mail.gmail.com' \
--to=yandros@gmail.com \
--cc=emacs-devel@gnu.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.