From: Juri Linkov <juri@linkov.net>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Michael Albinus <michael.albinus@gmx.de>, 45277@debbugs.gnu.org
Subject: bug#45277: SELECTION_CLEAR_EVENT crashes
Date: Tue, 13 Jul 2021 23:49:19 +0300 [thread overview]
Message-ID: <8735si54f4.fsf@mail.linkov.net> (raw)
In-Reply-To: <877djxlaor.fsf@gnus.org> (Lars Ingebrigtsen's message of "Mon, 17 May 2021 16:03:16 +0200")
>> I have exactly the same crashes on completely different computers.
>> What surprises me is that no one else has these crashes.
>
> OK, then it can hardly be a hardware issue. I can't recall seeing any
> other bug reports (from others) in this area, though, so it does seem
> like nobody else experiences these problems.
It seems these crashes are GC-related. They started to appear after Sep 2020.
And after recent GC-related changes there are no more crashes, but after
every screen lock/unlock, a produced DBUS event causes random errors.
Here are some examples:
Debugger entered--Lisp error: (wrong-type-argument number-or-marker-p ("\\.makepp\\'" . makefile-makepp-mode))
dbus-handle-event((dbus-event ("Makeppfile\\(?:\\.mk\\)?\\'" . makefile-makepp-mode) ...))
funcall-interactively(dbus-handle-event (dbus-event ("Makeppfile\\(?:\\.mk\\)?\\'" . makefile-makepp-mode) ...))
call-interactively(dbus-handle-event nil [(dbus-event ("Makeppfile\\(?:\\.mk\\)?\\'" . makefile-makepp-mode) ...)])
command-execute(dbus-handle-event nil [(dbus-event ("Makeppfile\\(?:\\.mk\\)?\\'" . makefile-makepp-mode) ...)] t)
Debugger entered--Lisp error: (wrong-type-argument listp "Monospace 10")
dbus-check-event((dbus-event :user-spec . "Monospace 10"))
dbus-handle-event((dbus-event :user-spec . "Monospace 10"))
funcall-interactively(dbus-handle-event (dbus-event :user-spec . "Monospace 10"))
call-interactively(dbus-handle-event nil [(dbus-event :user-spec . "Monospace 10")])
command-execute(dbus-handle-event nil [(dbus-event :user-spec . "Monospace 10")] t)
Debugger entered--Lisp error: (wrong-type-argument listp "#ffffffffffff")
dbus-handle-event((dbus-event background-color . "#ffffffffffff"))
funcall-interactively(dbus-handle-event (dbus-event background-color . "#ffffffffffff"))
call-interactively(dbus-handle-event nil [(dbus-event background-color . "#ffffffffffff")])
command-execute(dbus-handle-event nil [(dbus-event background-color . "#ffffffffffff")] t)
The last error contains part of (frame-parameter nil 'background-color) => "#ffffffffffff"
And after doing 'M-x garbage-collect' there are no more errors on screen lock/unlock.
Maybe GC-related changes didn't cause these errors, but just changed the behavior
of some memory leak in DBUS-related code?
next prev parent reply other threads:[~2021-07-13 20:49 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-16 20:58 bug#45277: D-Bus crashes and DND errors Juri Linkov
2020-12-17 18:38 ` Michael Albinus
2020-12-17 21:54 ` Juri Linkov
2020-12-18 10:22 ` Michael Albinus
2020-12-19 20:23 ` Juri Linkov
2020-12-20 20:01 ` Juri Linkov
2020-12-20 20:21 ` Michael Albinus
2020-12-28 17:03 ` Juri Linkov
2020-12-28 17:52 ` Michael Albinus
2020-12-28 18:19 ` Juri Linkov
2020-12-29 8:27 ` Michael Albinus
2020-12-29 9:31 ` Juri Linkov
2020-12-29 10:59 ` Michael Albinus
2020-12-29 15:16 ` Eli Zaretskii
2020-12-29 19:28 ` Juri Linkov
2020-12-30 10:21 ` Michael Albinus
2021-01-06 17:37 ` bug#45277: SELECTION_CLEAR_EVENT crashes Juri Linkov
2021-05-16 15:52 ` Lars Ingebrigtsen
2021-05-16 17:57 ` Juri Linkov
2021-05-17 14:03 ` Lars Ingebrigtsen
2021-07-13 20:49 ` Juri Linkov [this message]
2021-07-13 22:28 ` Juri Linkov
2021-07-13 22:34 ` Lars Ingebrigtsen
2020-12-21 8:59 ` bug#45277: DND errors Juri Linkov
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=8735si54f4.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=45277@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=michael.albinus@gmx.de \
/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).