Re: Memory leak detection (delete lines until 20 reproduces problem)

...there is a slow memory leak ... The first main problem I think is ... It seems impossible that ... Am I missing something? code itself is over 2000 lines

Reproduce the problem by slowly deleting 1980 lines until you're left with about 20 lines which reproduce the leak :)

Links on this type of stuff :)

Tutorials: Variable Scoping in Perl: the basics,
Coping with Scoping , Mini-Tutorial: Perl's Memory Management,
Lexical scoping like a fox,
Read this if you want to cut your development time in half!,
Closure on Closures , perlref#Circular References,
Memory leaks and circular references,
Circular references and Garbage collection.,
make perl release memory,
about memory management , Re^3: Scope of lexical variables in the main script , Re: What's the weaken here for?,
Devel::Cycle,
Devel::NYTProf,
Devel::Leak Devel::LeakTrace,
WeakRef

Comment on Re: Memory leak detection (delete lines until 20 reproduces problem)

Replies are listed 'Best First'.
Re^2: Memory leak detection (delete lines until 20 reproduces problem) by runnerup (Novice) on Sep 11, 2014 at 02:43 UTC
> Reproduce the problem by slowly deleting 1980 lines until you're left with about 20 lines which reproduce the leak :) To tell the truth, I can't even reproduce the problem without real users. Unfortunately I find it difficult to reproduce problems for socket-server code because it requires multiple users connected.	[reply]