how can I call a non-threadsafe module sub from multiple parallel spawned child threadsThere are no guarantees of course, but you're likely to have better results if you 'require' the problematic module within each child thread/process, rather than use/requiring it in the parent process - which causes its data to be copied to each child via thread cloning (which is how fork() is implemented on Windows perl).
Dave.
In reply to Re: Parallel::ForkManager dies with "Free to wrong pool..."
by dave_the_m
in thread Parallel::ForkManager dies with "Free to wrong pool..."
by perlygapes
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |