Re: threads hogging memory

Try modifying the line in your while loop to read

    threads->create( 'new_request', $client )->detach();
[download]

It won't fix all the problems, but it does reduce the memory consuption of your proxy substantially. You will still see long term memory growth, but the rate of growth is less than 1% of the unmodified code (based on very unscientific and insubstantial tests!).

Examine what is said, not who speaks.

"Efficiency is intelligent laziness." -David Dunham
"Think for yourself!" - Abigail

Comment on Re: threads hogging memory Download Code

Replies are listed 'Best First'.
Re^2: threads hogging memory by saskaqueer (Friar) on May 19, 2004 at 05:27 UTC
I had already tried such an approach. Changing that specific line yields the following slew of errors: Attempt to free unreferenced scalar: SV 0x280babe0 at c:/Perl/lib/IO/S +ocket.pm l ine 46, <GEN2> line 14. Attempt to free unreferenced scalar: SV 0x280babe0 at c:/Perl/site/lib +/Net/HTTP/ Methods.pm line 37, <GEN2> line 14. Attempt to free unreferenced scalar: SV 0x280babe0 at c:/Perl/site/lib +/Net/HTTP/ Methods.pm line 42, <GEN2> line 14. Attempt to free unreferenced scalar: SV 0x280babe0 at c:/Perl/lib/IO/S +ocket.pm l ine 46. Attempt to free unreferenced scalar: SV 0x280babe0 at c:/Perl/lib/IO/S +ocket.pm l ine 46, <GEN3> line 14. Attempt to free unreferenced scalar: SV 0x280babe0 at c:/Perl/site/lib +/Net/HTTP/ Methods.pm line 37, <GEN3> line 14. < snip > [download] After a few more such errors, Windows throws up a fatal error and the perl executeable exits. "This is perl, v5.8.2 built for MSWin32-x86-multi-thread" -- build 808, IThreads enabled.	[reply] [d/l]
Re: Re^2: threads hogging memory by BrowserUk (Patriarch) on May 19, 2004 at 05:33 UTC
Upgrade to AS 809, there is a patch specifically applied to correct that. `Locally applied patches: ActivePerl Build 809 22218 Remove the caveat about detached threads crashing on Win +dows 22201 Avoid threads+win32 crash by freeing Perl interpreter sl +ightly later 22169 Display 'out of memeory' errors using low-level I/O 22159 Upgrade to Time::Hires 1.55 22120 Make 'Configure -Dcf_by=...' work 22051 Upgrade to Time::HiRes 1.54 21540 Fix backward-compatibility issues in if.pm Built under MSWin32 Compiled at Feb 3 2004 00:28:51` [download] I see no errors at all using your (modified) code. I'm posting through it now. In fact, having navigated all the main subhead pages at news.bbc.co.uk, the memory usage is completely stable. The use rises and falls as I navigate, but stays remarkably stable at ~ 13 MB over time. Examine what is said, not who speaks. "Efficiency is intelligent laziness." -David Dunham "Think for yourself!" - Abigail	[reply] [d/l] [select]