[jdev] sm memory leaks
Bob Phan
bob at devianttechnologies.com
Tue Mar 2 16:28:58 CST 2004
On Tue, 2004-03-02 at 16:43, Robert Norris wrote:
> On Tue, Mar 02, 2004 at 01:08:29PM -0500, Bob Phan wrote:
>
> j2 is currently pretty lousy when it comes to memory management. It
> generally assumes that it can get as much memory as it wants. Certain
> things (eg the JID cache) are never freed or cleaned up, and can grow
> forever.
Is the JID cache part of the sm?
> A real memory management plan is being developed for the next round of
> server work, which should alleviate this.
How far along is this? Is there anything I can do to help out?
> As for dicovering real memory leaks, I suggest checking out
> http://valgrind.kde.org/ . I usually run it as:
>
> valgrind --skin=memcheck --num-callers=8 --leak-check=yes --show-reachable=yes
>
> Run the j2 pieces inside it, do your tests, and take a look at the
> valgrind logs when you're done. It will identify leaked memory.
Cool. I'll be messing with this this week. I hope to get as much of
the sm patched up as possible as quickly as possible.
Thanks for the help,
--
/*
* Bob Phan <bob at devianttechnologies.com>
* Code Master General
* Deviant Technologies Incorporated
* (203)458-2312
*
* http://www.devianttechnologies.com/
*/
More information about the JDev
mailing list