in reply to Fixing leaks with a flush memory call in perl?

How is that possible?
Mostly, my code calls variables into the main namespace (without using my) the program closes and i'm guessing the allocations stay open b/c of lack of "my".
If the program closes, how can "allocations stay open" (whatever that may mean)?

Here's how it works, your web server starts your perl program, writes stuff on your program's STDIN, reads off your programs STDOUT, and transmits that info to the client (hello HTTP). When your program ends, all the memory it was using is freed (on one of my apaches on win32, apache actually leaks memory every time it runs a perl/cgi program).

You wouldn't happen to be using mod_perl by any chance? If so you shouldn't run this program (I wouldn't).

There is no "flush" command (perl memory managment doesn't work like that). You have to fixup/rewrite your program, or live with it.

MJD says "you can't just make shit up and expect the computer to know what you mean, retardo!"
I run a Win32 PPM repository for perl 5.6.x and 5.8.x -- I take requests (README).
** The third rule of perl club is a statement of fact: pod is sexy.

  • Comment on Re: Fixing leaks with a flush memory call in perl?