in reply to Re: Memory Leak with XBase?
in thread Memory Leak with XBase?

In our experience OO perl, running persistently 'leaks' ie you observe a consistent growth in memory usage over time despite the fact that there is not more internal data being stored by the widget.

I have come to realize that of late.

and calling it a leak is not entirely correct because if you push the system into swap these 'leaky' processes suddenly shrink to a small fraction of there size - unload the system so there is no swap and they stay small but slowly grow over time.

Well, on my system (linux) the above code will quickly (if the sleep function is removed) eat up 99% of the real memory and all of the swap, but continues to run.

Sometimes undef stuff helps. Rewriting it into a more functional style will probably work as well if it really matters. It will probably make no difference but in the close code you could make an undef change

You're right, it doesn't make a difference. But thanks for the advice, I don't have time to rewrite XBase unless I absolutely have to, which it looks like I will...

tigervamp

In Section Seekers of Perl Wisdom