[GE users] Memory leak in 6.1u2 ?

Andreas.Haas at Sun.COM Andreas.Haas at Sun.COM
Thu Nov 15 14:17:18 GMT 2007


Hi Richard,

On Thu, 15 Nov 2007, Richard Ems wrote:

> Andreas.Haas at Sun.COM wrote:
>
>> First step is to patch the source code and built the binaries.
>> You using lx24-amd64 right now?
>
> Yes!

you find your schedd binary under

    http://gridengine.sunsource.net/files/documents/7/160/sge_schedd.gz

the scheduler is identical with 6.1u2 for lx24-amd64 except for the 
patch below. What the patch does for you is (a) enable allocation 
recording at scheduler start-up time (b) disable it at shut-down time. 
Make sure MALLOC_TRACE is set in schedd's environment as described in 
mtrace(3), since otherwise no recording will happen.

My recommendation is to shut-down schedd once you observe memory
leaking. That way mtrace(3) will report almost only real leaks 
when it does the memory balance.

Regards,
Andreas

> cvs diff daemons/schedd/sge_schedd.c
Index: daemons/schedd/sge_schedd.c
===================================================================
RCS file: /cvs/gridengine/source/daemons/schedd/Attic/sge_schedd.c,v
retrieving revision 1.113
diff -r1.113 sge_schedd.c
41c41,43
< 
---
> #ifdef LINUX
> #include <mcheck.h>
> #endif
265a268,273
> #ifdef LINUX
>    if (getenv("MALLOC_TRACE")) {
>       mtrace();
>    }
> #endif
> 
381a390,395
> #ifdef LINUX
>    if (getenv("MALLOC_TRACE")) {
>       muntrace();
>    }
> #endif

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe at gridengine.sunsource.net
For additional commands, e-mail: users-help at gridengine.sunsource.net




More information about the gridengine-users mailing list