GNU bug report logs -
#17395
GC during idle time becomes fatal
Previous Next
Reported by: rms <at> gnu.org
Date: Sat, 3 May 2014 08:01:02 UTC
Severity: normal
Merged with 17406,
28279
Found in version 25.2
Fixed in version 26.1
Done: Glenn Morris <rgm <at> gnu.org>
Bug is archived. No further changes may be made.
Full log
View this message in rfc822 format
[[[ To any NSA and FBI agents reading my email: please consider ]]]
[[[ whether defending the US Constitution against all enemies, ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]
IOW, the problem is not that the GC is taking longer but that the memory
is filling up with many Lisp objects. You can try M-x profiler-start
RET mem RET ... use Emacs for a while ... M-x profiler-report.
I have tried this. I can't understand the answers, though. I did
profiler-report several times, and each time it displays more than a
meg. Once it reported over 7 meg.
I did it in a session where I did real work, and got this:
+ redisplay_internal (C function) 29,776,412 0%
tooltip-hide 8,215,721 0%
+ timer-event-handler 336,066 0%
+ compilation-sentinel 333,520 0%
+ isearch-pre-command-hook 262,144 0%
internal-timer-start-idle 140,161 0%
undefined 131,072 0%
+ compilation-filter 26,200 0%
clear-transient-map 4,120 0%
+ clear-transient-map 1,040 0%
+ clear-transient-map 1,040 0%
... 0 0%
+ command-execute -452333584 0%
But the problem had not happened.
You can also try the install memory-usage (from GNU ELPA)
How?
--
Dr Richard Stallman
President, Free Software Foundation
51 Franklin St
Boston MA 02110
USA
www.fsf.org www.gnu.org
Skype: No way! That's nonfree (freedom-denying) software.
Use Ekiga or an ordinary phone call.
This bug report was last modified 7 years and 236 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.