perl doesn't have "real" garbage collection. instead it uses refcounts. the idea is pretty simple. every variable/array/hash has a counter that is used to keep track of how many references point to it. when this reaches 0, the memory is freed. not as robust as real garbage collection but very efficient.
most memory leaks i've seen have been from arrays just getting constantly added to and not reset. if you have a loop somewhere in your code that does $i++ and then $stuff$i = "something else" take a close look and see if the array ever goes out of scope or is explicitly reset; if not, there's your problem. the quick and dirty refcount method is efficient but has a problem with self-referential data structures. if you have a hash with one of the elements being a reference to the hash itself, the refcount will never hit 0 by itself and the memory won't be freed unless you delete it manually. but i've never found self-referential data structures to be very common for basic apps so i'd look for ever-growing arrays first.
In reply to Re: memory usage/leaks
by thraxil
in thread memory usage/leaks
by smackdab
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |