http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58378
--- Comment #4 from Olivier Grisel <olivier.grisel at ensta dot org> --- Thanks for the explanation. Would you consider a solution that would preserve the state of the parent process and would just reset the thread pool data on the child? Otherwise we will have to consider that the way fork() is used in Python's multiprocessing module is really an abuse and that there is no way to safely use both openmp-libraries and Python multiprocessing in the same program safely.