Win32::Process::Info and threads

LineStown has asked for the wisdom of the Perl Monks concerning the following question:

Hello all

Could you help with perl?

I have next code (it is a mini version of trouble):

use strict;
use threads;
use Win32::Process::Info;

sub test
{
    print "1";
}

threads->create(\&test)->join();
[download]

Result: 1Free to wrong pool 2c3fd30 not 6a8eb0 during global destruction.

It happens after ->join()

It works without use Win32::Process::Info;

Win32::Process::Info need for getting command line of process.

Win32::Process::Info qw{NT} doesn't give all information.

Thanks

Comment on Win32::Process::Info and threads Select or Download Code

Replies are listed 'Best First'.
Re: Win32::Process::Info and threads by vr (Curate) on Jan 17, 2017 at 14:43 UTC
Looks like very old bug with `Win32::OLE` (which `Win32::Process::Info::WMI` "uses") being not thread safe. E.g.: Re: free to wrong pool while global destruction : windows perl environment. And, yes, your example works (i.e. no such error) if `Win32::Process::Info` is "required" inside a sub instead of "used" globally.	[reply] [d/l] [select]
Re^2: Win32::Process::Info and threads by LineStown (Initiate) on Jan 17, 2017 at 15:01 UTC
I have tried do this: `use strict; use warnings; use Data::Dumper; use threads; sub include_info { require 'Win32::Process::Info'; } sub test { print "1"; } include_info; my $tid = threads->create(\&test)->join();` [download] Result: Can't locate Win32::Process::Info in @INC But use works. Could you explain my mistake?	[reply] [d/l]
Re^3: Win32::Process::Info and threads by Corion (Patriarch) on Jan 17, 2017 at 15:04 UTC
See require: `require Win32::Process::Info; # without the quotes` [download]	[reply] [d/l]
Re^4: Win32::Process::Info and threads by LineStown (Initiate) on Jan 17, 2017 at 15:16 UTC
Re^3: Win32::Process::Info and threads by vr (Curate) on Jan 18, 2017 at 08:27 UTC
This `Win32::OLE` hates Perl's threads too much... Then I'm afraid there's no other option but something like `use strict; use warnings; use threads; use feature 'say'; sub test { my $s = 'say $_-> { CommandLine } for Win32::Process::Info-> new-> + GetProcInfo'; say qx( $^X -MWin32::Process::Info -E "$s" ); } threads-> create( \&test )-> join;` [download]	[reply] [d/l] [select]
Re^4: Win32::Process::Info and threads by LineStown (Initiate) on Jan 19, 2017 at 10:39 UTC
Re: Win32::Process::Info and threads by Anonymous Monk on Jan 17, 2017 at 15:46 UTC
From the Win32::Process::Info documentation: The WMI variant has various problems, known or suspected to be inherited from Win32::OLE. See "BUGS" for the gory details. The worst of these is that if you use fork(), you must disallow WMI completely by loading this module as follows: `use Win32::Process::Info qw{NT};`	[reply] [d/l]
Re: Win32::Process::Info and threads by LineStown (Initiate) on Jan 17, 2017 at 15:27 UTC
I have changed code, after require I used import `Win32::Process::Info->import(qw(GetProcInfo));` and I have got Error again: Free to wrong pool 2c3fd30 not 6a8eb0 during global destruction.	[reply] [d/l]