From: Eli Zaretskii <eliz@gnu.org>
To: Po Lu <luangruo@yahoo.com>
Cc: 55870@debbugs.gnu.org, larsi@gnus.org, brucelam1982pi@anche.no
Subject: bug#55870: GNU Emacs 26.3, Select All(C-x h) does not work
Date: Sun, 17 Jul 2022 13:08:16 +0300 [thread overview]
Message-ID: <834jzgqcfj.fsf@gnu.org> (raw)
In-Reply-To: <87k08cf7wu.fsf@yahoo.com> (message from Po Lu on Sun, 17 Jul 2022 16:41:21 +0800)
> From: Po Lu <luangruo@yahoo.com>
> Cc: brucelam1982pi@anche.no, larsi@gnus.org, 55870@debbugs.gnu.org
> Date: Sun, 17 Jul 2022 16:41:21 +0800
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> None in particular: we store the clipboard data locally, and other
> >> programs request different selection "targets" from Emacs depending on
> >> the coding system they want it in.
> >
> > So the memory growth in the OP's scenario is due to something we do
> > locally? Where's the code which "stores the clipboard data locally"?
>
> xselect.c. Look at the code which changes terminal->Vselection_alist in
> x_own_selection.
So the growing memory can only be explained by the consing of
selection_value onto terminal->Vselection_alist, where selection_value
is the text being copied by M-w?
> > Or maybe some external program does request the clipboard data on OP's
> > machine? Is there a way to know when that happens, and specifically
> > to know which data-type is being requested?
>
> The best way is to build xselect.c with TRACE_SELECTION defined to 1 in
> that file. Otherwise, tracing each of the functions in
> selection-converter-alist should work too, but will not catch requests
> for types Emacs does not know how to handle.
Can any of the potential requests in this situation allocate lots of
memory?
(I'm at the end of my wits here, and very close to declare this bug as
not reproducible, so any ideas for debugging it further are welcome.)
next prev parent reply other threads:[~2022-07-17 10:08 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-09 8:50 bug#55870: GNU Emacs 26.3, Select All(C-x h) does not work Bruce via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-09 14:57 ` Lars Ingebrigtsen
[not found] ` <1fc51cba-c767-2e5f-e0be-6e0f8d7d1df6@anche.no>
2022-06-10 12:44 ` Lars Ingebrigtsen
2022-07-11 11:01 ` Lars Ingebrigtsen
[not found] ` <92253b43-50a1-554e-de66-f31f0c423b1f@anche.no>
2022-07-12 12:11 ` Lars Ingebrigtsen
2022-07-13 3:01 ` Bruce via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-13 10:56 ` Lars Ingebrigtsen
2022-07-13 11:12 ` Visuwesh
2022-07-13 11:43 ` Eli Zaretskii
2022-07-14 9:50 ` Bruce via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-14 10:02 ` Lars Ingebrigtsen
2022-07-14 10:09 ` Bruce via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-14 10:13 ` Eli Zaretskii
2022-07-15 12:44 ` Bruce via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-15 13:03 ` Eli Zaretskii
2022-07-16 0:15 ` Bruce via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-16 5:37 ` Eli Zaretskii
2022-07-17 2:38 ` Bruce via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-17 6:37 ` Eli Zaretskii
2022-07-17 7:27 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-17 7:51 ` Eli Zaretskii
2022-07-17 8:41 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-17 10:08 ` Eli Zaretskii [this message]
2022-07-17 11:57 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-17 12:49 ` Eli Zaretskii
2022-07-17 13:07 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-18 0:27 ` Bruce via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-18 1:01 ` Bruce via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-18 0:24 ` Bruce via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-09 16:16 ` 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=834jzgqcfj.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=55870@debbugs.gnu.org \
--cc=brucelam1982pi@anche.no \
--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 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.