From: "Gerd Möllmann" <gerd.moellmann@gmail.com>
To: Andrea Corallo <acorallo@gnu.org>
Cc: Eli Zaretskii <eliz@gnu.org>,
yantar92@posteo.net, 70796@debbugs.gnu.org,
Tassilo Horn <tsdh@gnu.org>
Subject: bug#70796: 30.0.50; bug-reference-mode leading to constant GCing
Date: Mon, 17 Jun 2024 10:21:30 +0200 [thread overview]
Message-ID: <m2le34q8s5.fsf@pro2.fritz.box> (raw)
In-Reply-To: <yp1r0cwhu04.fsf@fencepost.gnu.org> (Andrea Corallo's message of "Mon, 17 Jun 2024 04:07:55 -0400")
Andrea Corallo <acorallo@gnu.org> writes:
> Andrea Corallo <acorallo@gnu.org> writes:
>
>> Eli Zaretskii <eliz@gnu.org> writes:
>>
>>>> From: Tassilo Horn <tsdh@gnu.org>
>>>> Cc: Eli Zaretskii <eliz@gnu.org>, 70796@debbugs.gnu.org, yantar92@posteo.net
>>>> Date: Sun, 16 Jun 2024 11:45:16 +0200
>>>>
>>>> Gerd Möllmann <gerd.moellmann@gmail.com> writes:
>>>>
>>>> > No progress in this matter from my side. I don't know what's going on.
>>>>
>>>> Same here. The issue went from "bug-reference-mode leading to constant
>>>> GC-ing" to "any (additional) function (including a no-op function) in
>>>> jit-lock-functions leads to constant GC-ing on MacOS but only with
>>>> native compilation and only when native-comp-speed > 0." I feel
>>>> responsible for bug-reference-mode but Mac-specific issues during
>>>> redisplay that only happen with native-compilation are out of by
>>>> expertise, sorry.
>>>
>>> Andrea, could you perhaps look into this?
>>
>> I'll be happy to look into it but I don't use MacOS and AFAIR Tassilo
>> mentioned it's not reproducible on x86 (GNU/Linux?).
>>
>> I'll give it try here as well, but also to me the reproducer itself is
>> not 100% clear.
>>
>> Andrea
>
> Okay, so this is what I tried:
>
> I bootstrapped two Emacs from current master (7be66d8223e) one
> --with-native-compilation=yes the other --with-native-compilation=no and
> boths with Gerd patch applied.
>
> Also I checkout current scratch/igc (2343d55dff4) to get igc.org.
>
> I then tried to run with boths native/non-native emacsen with:
>
> .../src/emacs -eval '(setq garbage-collection-messages t)' -Q ~/emacs4/admin/igc.org
>
>
> Once started looking in *Messages* I see 7 GC cycles in the the
> non-native build and 5 in the native one, also I can scroll without
> issues or other GC cycles.
>
> Note that only during the first start the native copiled Emacs did a
> number of GC cycles more to jit some code but I guess that's expected.
>
> Am I trying to repruduce this correctly?
Almost. After loading the Org file, please M-x goto-address-mode RET, or
M-x bug-reference-mode RET. In fact, registering anything with
jit-lock-register seems to have the same effect. Tassilo posted a
do-nothing example.
For me that is, because no one not on macOS/arm64 seems to see that.
prev parent reply other threads:[~2024-06-17 8:21 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
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 [this message]
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=m2le34q8s5.fsf@pro2.fritz.box \
--to=gerd.moellmann@gmail.com \
--cc=70796@debbugs.gnu.org \
--cc=acorallo@gnu.org \
--cc=eliz@gnu.org \
--cc=tsdh@gnu.org \
--cc=yantar92@posteo.net \
/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.