nd spend a few weeks grubbing through the
code. yechh.
-harshy
> From: Son Chang [mailto:[EMAIL PROTECTED]]
>
> I saw this fix in one of the mailing list archives and tried
> it but I'm still
> getting the memory leak.
>
> -son
>
> Quoting Harshy Wanigasekara
at can I do to fix this problem?
>
>-son
Heh, I just unsubscribed from the mailing list,
almost missed your question.
We ran into the exact same problem here.
Try:
http://forum.swarthmore.edu/epigone/modperl/groxbloiglim/03AB3CB11CBED3118A4
F009027B0C2B16B71A4@HAPPY
Our fix stops the chil
Hi again,
We managed to fix the problem described
below. The issue was the win32
porting code in perl. In the file
perl-5.6.0/win32/win32.h
commenting out the line:
#define ENV_IS_CASELESS
fixes the memory leak problem.
-harshy
> -Original Message-
> From: Harshy Waniga
e compiled with VC++ 6.0
I ran BoundsChecker on the apache executable in the
hopes of finding a single culprit, but found a
multitude of perl core routines allocate memory using
win32_malloc() in /perl5.6.0/win32/win32.c and
don't free it.
Anyone seen this before?
-harshy
--
Harshy Wanigasekara, Omneon Video Networks.
