Gnus development mailing list
 help / color / mirror / Atom feed
* something memory related definitely going on lately.
@ 2003-06-05 17:42 Wes Hardaker
  2003-06-06  4:32 ` John Paul Wallington
  2003-06-06  6:55 ` Kai Großjohann
  0 siblings, 2 replies; 4+ messages in thread
From: Wes Hardaker @ 2003-06-05 17:42 UTC (permalink / raw)



hardaker  1867  2.3 44.4 212296 113472 ?     S    06:29   5:49 xemacs -f gnus
                         ^^^^^^^^^^^^^

A 113Mb emacs is, um, not good (even for XEmacs).

My normal tricks, however, for finding memory leaks:

(progn
  (insert "\n")
  (mapcar (function (lambda (z)
		      (insert (format "%s:\n" (buffer-name z)))
		      (mapcar (function 
			       (lambda (x) (insert (format "  %s %s\n" 
							   (symbol-name (car x))
							   (cdr x))))) 
			      (buffer-memory-usage z)) z))
	  (buffer-list t)))

Doesn't turn up anything really really huge buffer wise...  Is there a
function to get a lits of all current variables in use?  That could
then help determine the size of maybe an "overweight" variable.
-- 
"In the bathtub of history the truth is harder to hold than the soap,
 and much more difficult to find."  -- Terry Pratchett



^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2003-10-18  1:35 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-06-05 17:42 something memory related definitely going on lately Wes Hardaker
2003-06-06  4:32 ` John Paul Wallington
2003-06-06  6:55 ` Kai Großjohann
2003-10-18  1:35   ` Lars Magne Ingebrigtsen

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).