GNU bug report logs - #12447
24.1.50; Stuck in garbage collection on OS X

Previous Next

Package: emacs;

Reported by: Harald Hanche-Olsen <hanche <at> math.ntnu.no>

Date: Fri, 14 Sep 2012 21:10:01 UTC

Severity: normal

Merged with 12326

Found in versions 24.1.50, 24.2.50

Done: Eli Zaretskii <eliz <at> gnu.org>

Bug is archived. No further changes may be made.

Full log


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

From: Dmitry Gutov <dgutov <at> yandex.ru>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 12447 <at> debbugs.gnu.org, hanche <at> math.ntnu.no
Subject: Re: bug#12447: 24.1.50; Stuck in garbage collection on OS X
Date: Sun, 16 Sep 2012 16:07:07 +0400
On 16.09.2012 15:53, Eli Zaretskii wrote:
>> Date: Sun, 16 Sep 2012 14:44:30 +0400
>> From: Dmitry Gutov <dgutov <at> yandex.ru>
>> CC: hanche <at> math.ntnu.no, 12447 <at> debbugs.gnu.org
>>
>> Like I wrote in 12326, AFAICT, the problem is that timer_check_2 doesn't
>> at any point check that Emacs is still idle. When run-with-idle-timer
>> calls (timer-activate-when-idle timer t), the new timer is added to the
>> list, timer_check_2 reaches is and runs it immediately because
>> 'timer_idleness_start_time' still has the same value.
>
> If that is the problem, then perhaps having timer_check_2 work on a
> copy of the list would solve the problem.  Did you try that?

I'm no C programmer, so I didn't try to fix it in C code. How would I 
make a copy of a list there?

But no, it probably won't: the "guilty" commit made timer_check_2 
actually return 0 after a timer fires (keeping true to the comment above 
it), so a local copy would serve no purpose.

Assuming it would've worked, though, wouldn't it make the second 
argument to 'timer-activate-when-idle' useless?




This bug report was last modified 12 years and 247 days ago.

Previous Next


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