threads crash on XP (in Tk script)

[MoshiachNow]

HI,

Running a Tk script on my XP I always get an error.

Code:
########################################################################################
#use warnings;
use strict;
use Win32::OLE qw( in );
use Win32::Lanman;
use Net:omain qw(hostname hostfqdn hostdomain);
use Socket 'inet_ntoa';
use Sys::Hostname 'hostname';
use Data::Validate::IP qw(is_ipv4);
use Net:ing;
use Tk;
use Tk::Text;
use Tk::Scrollbar;
use Tk:ane;
use threads;

threads->create(sub { print("I am a thread\n"); })->join();

Error:
I am a thread
Free to wrong pool 1822b00 not 222770 during global destruction.

Any ideas?
Thanks

 

[Brian Raven]

HI,

Running a Tk script on my XP I always get an error.

Code:
########################################################################################
#use warnings;
use strict;
use Win32::OLE qw( in );
use Win32::Lanman;
use Net:omain qw(hostname hostfqdn hostdomain);
use Socket 'inet_ntoa';
use Sys::Hostname 'hostname';
use Data::Validate::IP qw(is_ipv4);
use Net:ing;
use Tk;
use Tk::Text;
use Tk::Scrollbar;
use Tk:ane;
use threads;

threads->create(sub { print("I am a thread\n"); })->join();

Error:
I am a thread
Free to wrong pool 1822b00 not 222770 during global destruction.

Any ideas?

One idea would be that threads, and modules that are not thread safe
do not mix very well. I don't know about any of the other modules that
you use, but Tk is not thread safe.

HTH

 

[zentara]

One idea would be that threads, and modules that are not thread safe
do not mix very well. I don't know about any of the other modules that
you use, but Tk is not thread safe.

HTH

Yeah, but he has not invoked any Tk statements before he builds the
thread. It should work, and it does work fine on linux.

Tk will work fine with threads, IF you build the thread before invoking
any Tk statements, AND don't try to share objects across thread
boundaries.

But you are probably right, that one of the use statements is causing
it. I would try removing them all, and adding them back, 1 by 1, until
you find which one causes it.

 

[Brian Raven]

Yeah, but he has not invoked any Tk statements before he builds the
thread. It should work, and it does work fine on linux.

True, but I suspect that this is not real code, but a small example to
demonstrate the problem.

Tk will work fine with threads, IF you build the thread before invoking
any Tk statements, AND don't try to share objects across thread
boundaries.

Again true (I have done that myself), but those restrictions make it
more difficult to write decent code. Enough so that it is probably
better (IMHO) to consider alternative designs/modules first.

But you are probably right, that one of the use statements is causing
it. I would try removing them all, and adding them back, 1 by 1, until
you find which one causes it.

Which suggests that Tk is not the only thread unsafe module being
loaded. In which case, a single threaded approach may be less
problematic.

HTH

 

[zentara]

Which suggests that Tk is not the only thread unsafe module being
loaded. In which case, a single threaded approach may be less
problematic.

HTH

Yeah, Tk is often blasted as not being thread safe, but many other
modules are in the same boat.