Re: [Bug: 21.4.12] memory leak
junq <junq(a)ihubbell.com> writes:
Running without the init.el seems to stop the leakage. It's
possible that it is a problem (from what I've learned so far) from
the XAE that gets loaded via init.el XAE == Xml Authoring
Environment
xae-1.0beta8
http://xae.sunsite.dk/xae-beta.tar.gz
What makes you think that XAE is a problem? Does the leak fail to
occur if and only if you comment out the loading of XAE?
It would be really strange if XAE caused the leak without having an
itimer that would actually run. However, you never know what hooks it
might have installed that contain leaks. It could also be a genuine
XEmacs bug triggered by the XAE code, but I doubt it without any
evidence.
> 1. Run (while t (cperl-get-help-defer)) and monitor the XEmacs
process
> for signs of leakage. If you don't detect leaking in several
> minutes, there is probably no leak in that area.
Chewed on the cpu well enough but I observed no memory leak.
>
> 2. Run (run-with-idle-timer .1 t (lambda () nil)) and leave XEmacs for
> the night. See if you get the leaks.
This is running but it looks inocuous so far.
Then cperl-mode is probably not to blame.