in reply to free to wrong pool while global destruction : windows perl environment

The Win32::OLE module is not safe for use in threaded Perl. You _may_ be able to get by if you only use Win32::OLE inside a single thread *if* you load Win32::OLE inside that thread. But loading Win32::OLE and then creating additional Perl interpreter threads is going to blow up.
  • Comment on Re: free to wrong pool while global destruction : windows perl environment

Replies are listed 'Best First'.
Re^2: free to wrong pool while global destruction : windows perl environment
by Davewhite (Acolyte) on Jul 27, 2009 at 08:29 UTC

    Thanks for the reply

    My requirement is to create the thread after OLE access in main thread

    Following is my requirement :

    1. Connect to the CANAlyzer using OLE in perl script.

    2. Perform test execution using CANAlyzer, in a loop and start a parallel thread to perform some file processing and save the log for test execution.

    Is there any other approach to perform parallel processing apart from threads.( fork won't work in windows perl )

      fork() does work, somewhat in Windows Perl, but as it is implemented using threads on Windows, it won't work for you because of the same reason that threads don't work for your problem.

      The best way, as jand already described, is to load Win32::OLE in a second thread, and to not have Win32::OLE in the main thread. You will need to restructure your program so it works that way.

      Alternatively, consider having two programs, one that talks to CANAlyzer, and one that talks to TeraTerm. The two programs then can talk to each other through files, pipes (via IPC::Open3 for example), or sockets. This is not trivial either, but might provide a way forward for you.


        Thanks for the suggestions.

        Both the approaches are good. But, I will give a try to seperate program approach, as the TTerm will stop the further test execution ( as it's waiting for event to occur), if brought into main thread.