I suspect our current setup of mod_perl is leaking memory, most likely due to bad C/C++ libraries somewhere.  I came to this conclusion after days of research and testing. I setup a very very thin version of apache 1.3.34 with mod_perl compiled statically. I have an ever thinner handler that just prints hello, world.  I also have a similiar setup on a FreeBSD machine. After hitting the same uri, the linux machine leaks 4k per request, while the FreeBSD DOES NOT. 

I also tried another different kind of test. I setup mod_perl as a DSO. I wrote a C content handler (hello, world). I also used the same thin mod_perl handler (hello, world). When hitting the C handler, no leaks. When hitting the mod_perl handler, again a 4k leak on every request.

Now I read the practical mod_perl book several times over and over, and it talks about having C/C++ leaks. Now that I am sure its not our codebase (due to the fact its just an hello, world handler), I am confident its something beyond the code.

So how can I go about identifying which external linked libraries are the culprit? And does anyone else have any experience with this types of leaks on linux machines?

This is our setup:

Linux: 2.6.9-34.EL.rev1.AM.smp #1 SMP

osname=linux, osvers=2.6.12-1.1372_fc3smp, archname=x86_64-linux
    uname='linux host_here 2.6.12-1.1372_fc3smp #1 smp fri jul 15 01:08:54 edt 2005 x86_64 x86_64 x86_64 gnulinux '
    config_args='-des -Dprefix=/usr/local -Dlibperl=libperl.so -Duseshrplib -Dinstallusrbinperl -Duselargefiles -Doptimize=-O3 -funroll-loops -march=opteron -msse2 -fomit-frame-pointer -Dinc_version_list=5.8.4/i686-linux 5.8.4 -Dmyhostname=localhost [EMAIL PROTECTED]'
    hint=recommended, useposix=true, d_sigaction=define
    usethreads=undef use5005threads=undef useithreads=undef usemultiplicity=undef
    useperlio=define d_sfio=undef uselargefiles=define usesocks=undef
    use64bitint=define use64bitall=define uselongdouble=undef
    usemymalloc=n, bincompat5005=undef
  Compiler:
    cc='cc', ccflags ='-fno-strict-aliasing -pipe -I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -I/usr/include/gdbm',
    optimize='-O3 -funroll-loops -march=opteron -msse2 -fomit-frame-pointer',
    cppflags='-fno-strict-aliasing -pipe -I/usr/local/include -I/usr/include/gdbm'
    ccversion='', gccversion='3.4.3 20050227 (Red Hat 3.4.3-22.1)', gccosandvers=''
    intsize=4, longsize=8, ptrsize=8, doublesize=8, byteorder=12345678
    d_longlong=define, longlongsize=8, d_longdbl=define, longdblsize=16
    ivtype='long', ivsize=8, nvtype='double', nvsize=8, Off_t='off_t', lseeksize=8
    alignbytes=8, prototype=define
  Linker and Libraries:
    ld='cc', ldflags =' -L/usr/local/lib'
    libpth=/usr/local/lib /lib /usr/lib
    libs=-lnsl -ldl -lm -lcrypt -lutil -lc
    perllibs=-lnsl -ldl -lm -lcrypt -lutil -lc
    libc=/lib/libc-2.3.4.so, so=so, useshrplib=true, libperl=libperl.so
    gnulibc_version='2.3.4'
  Dynamic Linking:
    dlsrc=dl_dlopen.xs, dlext=so, d_dlsymun=undef, ccdlflags='-Wl,-E -Wl,-rpath,/usr/local/lib/perl5/5.8.6/x86_64-linux/CORE'
    cccdlflags='-fpic', lddlflags='-shared -L/usr/local/lib'


Characteristics of this binary (from libperl):
  Compile-time options: USE_64_BIT_INT USE_64_BIT_ALL USE_LARGE_FILES
  Built under linux
  Compiled at Aug 24 2005 14:02:33
  @INC:
    /usr/local/lib/perl5/5.8.6/x86_64-linux
    /usr/local/lib/perl5/5.8.6
    /usr/local/lib/perl5/site_perl/5.8.6/x86_64-linux
    /usr/local/lib/perl5/site_perl/5.8.6
    /usr/local/lib/perl5/site_perl

__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com

Reply via email to