[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#45277: SELECTION_CLEAR_EVENT crashes
From: |
Lars Ingebrigtsen |
Subject: |
bug#45277: SELECTION_CLEAR_EVENT crashes |
Date: |
Wed, 14 Jul 2021 00:34:38 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) |
Juri Linkov <juri@linkov.net> writes:
>>> 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 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?
Hm, might be. I've added Paul to the CCs -- perhaps he has some input
here?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no