http://www.perlmonks.org?node_id=1151010


in reply to Re^2: Win32::Daemon memory leak
in thread win32::daemon memory leak

I'm interested in the matter (abandoned services in Perl since the day of "service could not start in a timely fashion".. error)
I have installed your service and now i'm monitoring it for the next 4 hours, with:
#PID perl -E "for(1..240){system qq(tasklist /fi \"PID eq 17360\" /n +h);sleep 60}" # UPDATE: RESULTS perl.exe 17360 Services 0 + 9.136 K # 240x60 sec after.. perl.exe 17360 Services 0 + 16.768 K #it leaked 31.8K every minute

UPDATE: The increment seems to me constant over time even if not so regular:
perl -lanE "$res{$F[-2]}++;END{print map{qq($_ = $res{$_}\n)} sort {$a +<=>$b} keys %res}" c:\SCRIPTS\leakedmemory.log = 283 # blanks lines emitted by 'tasklist' 9.136 = 1 9.268 = 4 9.396 = 4 9.572 = 1 9.720 = 4 9.848 = 4 9.976 = 4 10.104 = 4 10.360 = 8 10.488 = 4 10.616 = 5 10.744 = 4 10.872 = 4 11.128 = 8 11.384 = 8 11.644 = 9 11.900 = 8 12.156 = 9 12.412 = 8 12.668 = 8 12.924 = 9 13.184 = 8 13.440 = 8 13.696 = 8 13.700 = 1 13.952 = 8 14.208 = 8 14.464 = 9 14.720 = 8 14.724 = 1 14.976 = 8 15.236 = 8 15.492 = 8 15.496 = 1 15.748 = 8 16.004 = 6 16.008 = 1 16.256 = 1 16.260 = 6 16.512 = 9 16.768 = 5
The leak even if little is yet noticeable: the working set is passed fro 9.136K to 9.848K in 15 minutes. Private bytes also are arising. I'm using also Process Explorer. I think you need to investigate further. Have you some holidays? look at this article: identifying-memory-leak-with-process-explorer-and-windbg and share your results! in the meantime I have not enough time to investigate.
I'll tell you more

L*
There are no rules, there are no thumbs..
Reinvent the wheel, then learn The Wheel; may be one day you reinvent one of THE WHEELS.

Replies are listed 'Best First'.
Re^4: Win32::Daemon memory leak
by tbsky (Novice) on Dec 23, 2015 at 09:48 UTC
    thanks for the hint. I will spent my time to read your suggestion!