here's my $.02 on this subject. Correct me if I am wrong. Once perl uses memory it does not want to let it go back to the system. I believe I have read the the developers are working on this. Since you have your script running as a daemon. It will not release a lot of memory back to the system, if any at all.
I had a similar problem. The way I worked around it is: I knew where my script was eating up memory. So at these point I fork() children. Once the child completes and dies the memory is released back into the system. at least I saw a dramatic decrease in memory consumption. --chad On Fri, 2002-09-20 at 04:08, Timothy Johnson wrote: > > Instead of delete()ing it, try lexically scoping your hashes using my(). > You may find that letting the data structures go out of scope releases some > memory to be reused by perl that you were missing. > > -----Original Message----- > From: Angerstein [mailto:[EMAIL PROTECTED]] > Sent: Friday, September 20, 2002 12:30 AM > To: [EMAIL PROTECTED] > Subject: how to find memory leaks? > > > Hi, > I have a deamon like programm, which runs tasks at give timestamps. > This is in a while (1) {} if startjobx == time loop. > > Now i have the problem that one or more of my datastructures eats more and > more memory. > I "delete" every value after using it from my hashes or array from arrays, > but it still not getting better. any idea? > > > -- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > -- The instructions said to use windows 98 or better, so I installed slackware.
signature.asc
Description: This is a digitally signed message part
