At 13:47 +0530 12/4/02, Aravind Srivaths wrote:
I am using perl threads for developing a simulator and ran into the memory leak. I've gone 90% of the way with Perl, so, given the time I've invested, I'd like to see it through. I would like to contribute to fixing the problem.
That is good news!
The fact that shared arrays specifically are leaking memory (and possibly shared hashes as well) is known and has been reported. Have you found other memory leaks?... Does anybody have a good estimate of the complexity of the problem? Is it some basic issue with the way threads are implemented or is it a simple issue that hasn't come up the bug list or does nobody know?
I understand Arthur Bergman is working on the problem. It will be there when it is there, unless someone else beats him to it.... I'd appreciate your input on how much time it would take someone (a person who understands the code and a complete beginner) to fix this as that would help me make the decision to stick to perl or try something else for the time being.
<plug>
As a personal attempt to get around these problems in the ithreads implementation, I started developing forks.pm, which emulates Perl threads using fork. It is fully functional apart from the :shared attribute (shared variables _do_ work, you just cannot make them shared with the :shared attribute).
</plug>
Hope this helps.
Liz
