From: "Gerd Möllmann" <gerd.moellmann@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 70796@debbugs.gnu.org
Subject: bug#70796: 30.0.50; bug-reference-mode leading to constant GCing
Date: Mon, 06 May 2024 14:35:42 +0200 [thread overview]
Message-ID: <m28r0nunhd.fsf@pro2.fritz.box> (raw)
In-Reply-To: <86ttjbb1pu.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 06 May 2024 14:48:29 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Gerd Möllmann <gerd.moellmann@gmail.com>
>> Date: Mon, 06 May 2024 08:53:29 +0200
>>
>> This is in an Emacs compiled from the branch scratch/igc, but I see the
>> same in master.
>>
>> When loading admin/igc.org in scratch/igc I see very frequent GC, even
>> while doing nothing at all. Memory profiler shows this
>>
>> 4,192,076,326 68% - redisplay_internal (C function)
>> 2,997,520,400 48% - jit-lock-function
>> 2,997,520,400 48% - jit-lock-fontify-now
>> 2,982,457,616 48% - jit-lock--run-functions
>> 2,982,457,616 48% - run-hook-wrapped
>> 2,982,457,616 48% - #<compiled-function 8A7>
>> 2,769,181,376 45% - font-lock-fontify-region
>> 2,769,181,376 45% - font-lock-default-fontify-region
>> 2,707,362,176 44% - font-lock-fontify-keywords-region
>> 276,400,512 4% + org-do-emphasis-faces
>> 197,821,440 3% + org-fontify-drawers
>> 197,821,440 3% + org-activate-links
>> 197,821,440 3% + org-activate-tags
>> 197,821,440 3% + org-activate-dates
>> 197,821,440 3% + org-activate-footnote-links
>> 197,821,440 3% + org-fontify-macros
>> 197,821,440 3% + org-font-lock-add-priority-faces
>> 197,821,440 3% + org-do-latex-and-related
>> 197,821,440 3% + org-activate-code
>> 197,821,440 3% + org-fontify-meta-lines-and-blocks
>> 197,821,440 3% + org-fontify-inline-src-blocks
>> 197,821,440 3% + org-cite-activate
>> 57,104,384 0% re-search-forward
>> 61,819,200 1% + font-lock-unfontify-region
>> 213,276,240 3% + bug-reference-fontify
>> 15,062,784 0% - run-with-timer
>> 15,062,784 0% + apply
>> 97,280 0% + file-remote-p
>> 336 0% + desktop-auto-save-set-timer
>> 144 0% + tab-bar-make-keymap
>> 1,955,072,562 31% + command-execute
>> 129,456 0% + timer-event-handler
>> 1,024 0% + corfu--auto-post-command
>> 0 0% ...
>
> Where's the evidence of "frequent GC" in this profile?
I didn't say the profile is evidence of frequent GCs.
> (And "memory profile" has nothing to do with memory usage, contrary to
> popular belief.)
>
>> Disabling bug-reference-mode in the Org buffer makes it stop constantly
>> GCing.
>
> I believe you. But showing the number of GCs (e.g., using the
> variable gcs-done) would tell us the story more convincingly.
> Alternatively, if you can share an Org file where this could be seen,
> please do.
So, believe me. Or not, as you please. I said where the Org file is at
the beginning.
next prev parent reply other threads:[~2024-05-06 12:35 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-06 6:53 bug#70796: 30.0.50; bug-reference-mode leading to constant GCing Gerd Möllmann
2024-05-06 11:48 ` Eli Zaretskii
2024-05-06 12:35 ` Gerd Möllmann [this message]
2024-05-06 14:03 ` Eli Zaretskii
2024-05-06 14:09 ` Gerd Möllmann
2024-05-07 6:58 ` Gerd Möllmann
2024-05-18 6:27 ` Gerd Möllmann
2024-05-18 8:07 ` Eli Zaretskii
2024-05-18 15:49 ` Tassilo Horn
2024-05-24 20:00 ` Tassilo Horn
2024-05-24 20:19 ` Gerd Möllmann
2024-05-24 20:28 ` Ihor Radchenko
2024-05-25 4:08 ` Gerd Möllmann
2024-05-24 21:34 ` Tassilo Horn
2024-05-25 4:34 ` Gerd Möllmann
2024-05-25 7:37 ` Tassilo Horn
2024-05-25 7:58 ` Gerd Möllmann
2024-05-25 8:17 ` Tassilo Horn
2024-06-01 9:05 ` Gerd Möllmann
2024-06-15 7:54 ` Eli Zaretskii
2024-06-15 8:07 ` Gerd Möllmann
2024-06-16 9:45 ` Tassilo Horn
2024-06-16 10:44 ` Eli Zaretskii
2024-06-17 7:34 ` Andrea Corallo
2024-06-17 8:07 ` Andrea Corallo
2024-06-17 8:19 ` Tassilo Horn
2024-06-17 8:30 ` Andrea Corallo
2024-06-17 9:02 ` Gerd Möllmann
2024-06-17 9:30 ` Andrea Corallo
2024-06-17 9:53 ` Gerd Möllmann
2024-06-17 10:10 ` Andrea Corallo
2024-06-17 10:33 ` Gerd Möllmann
2024-06-17 14:13 ` Andrea Corallo
2024-06-17 8:21 ` Gerd Möllmann
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=m28r0nunhd.fsf@pro2.fritz.box \
--to=gerd.moellmann@gmail.com \
--cc=70796@debbugs.gnu.org \
--cc=eliz@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 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).