in reply to Re^5: Threads calling LWP causes exception
in thread Threads calling LWP causes exception

Well this is real interesting. I setup a Windows 2003 Server without MS VS .NET 2003 installed on it. The Perl code works fine. I guess I'll move to a different dubugger soon. BTW, how can I get rid of the "Scalars leaked"?
  • Comment on Re^6: Threads calling LWP causes exception

Replies are listed 'Best First'.
Re^7: Threads calling LWP causes exception
by BrowserUk (Patriarch) on Mar 10, 2006 at 20:55 UTC
    I setup a Windows 2003 Server without MS VS .NET 2003 installed on it. The Perl code works fine.

    Strange, but not entirely surprising. AS is built with VC++ v6, and I continue to build anything intended for use with Perl using the same compiler. Theoretically unnecessary, but maybe my instincts are good :)

    BTW, how can I get rid of the "Scalars leaked"?

    Change your LetsRock sub to call threads->create directly instead of via your (rather useless. Sorry:), Thread wrapper and the problem goes away.

    sub LetsRock { my (@kids); for (my $x=0; $x < 10; $x++) { my ($kid) = threads->create( \&ThreadFunc, 'https://www.wellsf +argo.com'); if (defined($kid)) { push(@kids, $kid); } sleep(1); } WaitForThreads(@kids); }

    Leaked scalars generally seem to be related to the use of variables passed to the thread through closure (as of 5.8.6 at least). Using the asynch() function seems particularly prone to this. Quite why this

    sub Thread { my ($function, @params) = @_; my ($thread); if (defined(&{$function})) { $thread = threads->create($function, @params); } return($thread); }

    causes a leaked scalar I'm not sure, maybe the defined(&{$function}), but I fail to see the benefit of that piece of indirection anyway? In fact, the whole sub seems pretty redundant to me.


    Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
    Lingua non convalesco, consenesco et abolesco. -- Rule 1 has a caveat! -- Who broke the cabal?
    "Science is about questioning the status quo. Questioning authority".
    In the absence of evidence, opinion is indistinguishable from prejudice.
      Thanks for your help.
        Would you mind running this code with a command line of "https://www.wellsfargo.com" ? I have a feeling that Crypt-SSLeay is not thread safe.
        package perl_module1; use strict; use v5.8; use HTTP::Cookies; use LWP::UserAgent; use HTTP::Request::Common; use URI::Escape; use vars qw(@ISA @EXPORT); use Exporter (); our @ISA = qw(Exporter); our @EXPORT = qw( GetIt ); our $DEBUG = 0; sub GetIt { my ($url) = @_; my ($ua) = LWP::UserAgent->new(keep_alive => 1); $ua->timeout(60); # allow redirects for POST push @{ $ua->requests_redirectable }, 'POST'; # set the cookie my ($cookie) = './ac_cookie.txt' . $$; $ua->cookie_jar(HTTP::Cookies->new('file' => $cookie)); my ($response) = $ua->get($url); if ($response->is_success) { my ($page) = $response->content; print( $page ); } else { printf "Failed with %s\n", $response->message; } } return 1 if caller; package main; use strict; use warnings; use v5.8; use threads; use threads::shared; print("Starting LetsRock() \n"); ThreadFunc( $ARGV[ 0 ] ); LetsRock( $ARGV[ 0 ] ); print("LetsRock() ended \n"); exit(0); sub LetsRock { my $url = shift; my (@kids); for (my $x=0; $x < 5; $x++) { my ($kid) = threads->create( \&ThreadFunc, $url ); if (defined($kid)) { push(@kids, $kid); } sleep(1); } printf "Waiting for %s\n", $_->tid, $_->join for @kids; } sub ThreadFunc { return perl_module1::GetIt( $_[0] ); } __END__