|
From: | Jason Rumney |
Subject: | Re: Memory leak? |
Date: | Mon, 18 Sep 2006 01:18:19 +0100 |
User-agent: | Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.8.0.4) Gecko/20060516 Thunderbird/1.5.0.4 Mnenhy/0.7.4.666 |
Jason Rumney wrote:
The problem seems to be caused by this fix:Andreas Roehler <address@hidden> writes:Sorry, it's not the memory, it's the CPU which is taken.Do you use semantic? There have been a couple of reports recently about semantic's idle timer functions taking 100% CPU on recent CVS versions of Emacs. 2006-08-20 Richard Stallman <address@hidden> * emacs-lisp/timer.el (run-with-idle-timer): Pass t to timer-activate-when-idle, so timer can run before Emacs becomes non-idle again. After reverting that fix, I see Emacs CPU usage go from 0 to 2% for a brief instant when the idle timers kick in. With that fix, the CPU usage goes to 50% and stays there until I perform an input event to break the idle loop. |
[Prev in Thread] | Current Thread | [Next in Thread] |