all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
* How to debug elisp memory leak
@ 2004-09-16 14:45 Frode Vatvedt Fjeld
  2004-09-17 18:14 ` Stefan Monnier
  2004-10-03 12:53 ` Florian Weimer
  0 siblings, 2 replies; 8+ messages in thread
From: Frode Vatvedt Fjeld @ 2004-09-16 14:45 UTC (permalink / raw)


I'm regularly getting the "lisp pointer size exceeded" warning after
about one week of running emacs. When this happens, nothing I do, such
as killing buffers, seems to help much; at most I can postpone the
inevitable crash for a few more minutes of work.

I figure there's a memory leak; somewhere there's e.g a global
variable with an ever-growing list of whatever. But I have no idea
where to start looking for what or where this might be. Can anyone
help me?

I'm using GNU Emacs 21.3.1, but this behavior has been consistent for
at least a few months and minor versions of emacs.

Thanks,
-- 
Frode Vatvedt Fjeld

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

end of thread, other threads:[~2004-10-04 14:33 UTC | newest]

Thread overview: 8+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-09-16 14:45 How to debug elisp memory leak Frode Vatvedt Fjeld
2004-09-17 18:14 ` Stefan Monnier
2004-09-20 12:23   ` Frode Vatvedt Fjeld
2004-10-02 10:33     ` Frode Vatvedt Fjeld
2004-10-02 10:51       ` Frode Vatvedt Fjeld
2004-10-02 11:15     ` Frode Vatvedt Fjeld
2004-10-04 14:33       ` Stefan Monnier
2004-10-03 12:53 ` Florian Weimer

Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.