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 #61 received at 12447 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Dmitry Gutov <dgutov <at> yandex.ru>
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 17:54:36 +0300
> Date: Sun, 16 Sep 2012 18:25:50 +0400
> From: Dmitry Gutov <dgutov <at> yandex.ru>
> CC: hanche <at> math.ntnu.no, 12447 <at> debbugs.gnu.org
> 
> > Perhaps the problem is that the value of 'difference' is not
> > initialized:
> >
> >    while (CONSP (timers) || CONSP (idle_timers))
> >      {
> >        Lisp_Object timer = Qnil, idle_timer = Qnil;
> >        EMACS_TIME timer_time, idle_timer_time;
> >        EMACS_TIME difference;   <<<<<<<<<<<<<<<<<<<<<<<<<<<<
> >
> > and then never set to any specific value, until here:
> >
> >        else
> > 	/* When we encounter a timer that is still waiting,
> > 	   return the amount of time to wait before it is ripe.  */
> > 	{
> > 	  UNGCPRO;
> > 	  return difference;
> > 	}
> >
> > which causes us return garbage, potentially zero, to timer_check.
> 
> It's assigned to, though. When we encounter a timer that's not yet ripe.

What if all of them are ripe?




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.