Re: Memory again

[YAMAMOTO Mitsuharu]

> Other than running valgrind on temacs, load everything in and then
> print out reachable memory, I don't know how to check this.  It
> sounds as it isn't a leak as such, but something that is still
> referenced, but not needed.

The `heap' command might give some help.  Perhaps one can compare
results of `heaps -addresses all <pid>' between before and after a VM
invocation as explained in the manual page, and then use
`malloc_history' to show the stack trace.

                                     YAMAMOTO Mitsuharu
                                address@hidden