GNU bug report logs - #70796
30.0.50; bug-reference-mode leading to constant GCing

Previous Next

Full log

Message #29 received at 70796 <at> debbugs.gnu.org (full text, mbox):

From: "Tassilo Horn" <tsdh <at> gnu.org>
To: "Eli Zaretskii" <eliz <at> gnu.org>,
 Gerd Möllmann <gerd.moellmann <at> gmail.com>
Cc: yantar92 <at> posteo.net, 70796 <at> debbugs.gnu.org
Subject: Re: bug#70796: 30.0.50; bug-reference-mode leading to constant GCing
Date: Sat, 18 May 2024 17:49:15 +0200

Hi all,

it's the first day of my vacation so I'm away from the computer until next Saturday evening at best. But then I'll have a look. 

Bye, 
Tassilo 

Am Sa, 18. Mai 2024, um 10:07, schrieb Eli Zaretskii:
>> From: Gerd Möllmann <gerd.moellmann <at> gmail.com>
>> Cc: Ihor Radchenko <yantar92 <at> posteo.net>,  70796 <at> debbugs.gnu.org
>> Date: Sat, 18 May 2024 08:27:15 +0200
>> 
>> Gerd Möllmann <gerd.moellmann <at> gmail.com> writes:
>> 
>> > Gerd Möllmann <gerd.moellmann <at> gmail.com> writes:
>> >
>> >> Eli Zaretskii <eliz <at> gnu.org> writes:
>> >>
>> >>> So I'm not sure which part(s) of bug-reference.el make a lot of
>> >>> garbage, or why.
>> >>
>> >> This maybe completely wrong, but my suspicion was that bug-reference
>> >> somehow triggers Org fontification, which creates more garbage. If
>> >> that's possible...
>> >
>> > Maybe bug-reference-fontify should return a list (jit-lock-bounds beg
>> > end)? Looks to me like if it doesn't we could end up fontifying the
>> > whole buffer for Org. See jit-lock--run-functions.
>> >
>> > Not sure but the behaviour looks like somethign like that could be
>> > happening.
>> 
>> Ping
>
> Tassilo, could you please take a look at this?

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.