Bookmarks

Yahoo Gmail Google Facebook Delicious Twitter Reddit Stumpleupon Myspace Digg

Search queries

wwwxxx0cm, www.webdp.net, Event 9 IIS log failed to write entry, wwwxxx jeffs, Catastrophic failure Unexpected method call sequence. 0x8000ffff (-2147418113)., ksh lock a file, [unixODBC][Driver Manager]Driver's SQLAllocHandle on SQL_HANDLE_DBC failed, sed: -e expression #1, char 1: unterminated address regex, procmail + change subject, w2ksp4.exe download

Links

XODOX
Impressum

#1: memory leaks

Posted on 2006-06-28 23:20:17 by jonathan vanasco

i'm using Crypt::OpenSSL::RSA

it has a memory leak when generating keys > 512
i generate keys 1024

i'm thinking that using sizelimit (i already do) should reclaim the
memory every so often when the child dies

unless the memory leak is happening elsewhere, not sure. i only call
the routines after fork though.

thoughts?


| - - - - - - - - - - - - - - - - - - - -
| RoadSound.com / Indie-Rock.net
| Collaborative Online Management And Syndication Tools
| - - - - - - - - - - - - - - - - - - - -

Report this message

#2: Re: memory leaks

Posted on 2006-06-29 00:30:20 by pgollucci

Jonathan Vanasco wrote:
>
> i'm using Crypt::OpenSSL::RSA
>
> it has a memory leak when generating keys > 512
> i generate keys 1024
>
> i'm thinking that using sizelimit (i already do) should reclaim the
> memory every so often when the child dies
>
> unless the memory leak is happening elsewhere, not sure. i only call
> the routines after fork though.
>
> thoughts?
Try valgrind or possibly Apache::Leak ?

if you mean like a system() fork then it should be reclaimed when the process is done.

--
------------------------------------------------------------ ------------
Philip M. Gollucci (pgollucci@p6m7g8.com) 323.219.4708
Consultant / http://p6m7g8.net/Resume/resume.shtml
Senior Software Engineer - TicketMaster - http://ticketmaster.com
1024D/A79997FA F357 0FDD 2301 6296 690F 6A47 D55A 7172 A799 97F

"It takes a minute to have a crush on someone, an hour to like someone,
and a day to love someone, but it takes a lifetime to forget someone..."

Report this message

#3: Re: memory leaks

Posted on 2006-06-29 01:31:03 by jonathan vanasco

On Jun 28, 2006, at 6:30 PM, Philip M. Gollucci wrote:

> Jonathan Vanasco wrote:
>> i'm using Crypt::OpenSSL::RSA
>> it has a memory leak when generating keys > 512
>> i generate keys 1024
>> i'm thinking that using sizelimit (i already do) should reclaim
>> the memory every so often when the child dies
>> unless the memory leak is happening elsewhere, not sure. i only
>> call the routines after fork though.
>> thoughts?
> Try valgrind or possibly Apache::Leak ?
>
> if you mean like a system() fork then it should be reclaimed when
> the process is done.

sorry, i meant i only call after apache forks

i know the module leaks and there's nothing i can do about that...

but apache::leak might be able to tell me what's going on if i can
write a test to generate a bunch of keys and track memory before and
after sizelimit kills the child


| - - - - - - - - - - - - - - - - - - - -
| RoadSound.com / Indie-Rock.net
| Collaborative Online Management And Syndication Tools
| - - - - - - - - - - - - - - - - - - - -

Report this message