For Photoshop's prior to CC (CS5, CS6 for example) I place "libomp5md.dll" into Photoshop directory. For Photoshop's higher than CC I use "libomp5md.dll" that delivered with Photoshop.
Also I tried to compile "libomp" from scratch, but nothing changes in speed or other behavior.
TRANTOR, I have the strange case where I run 2 different plug in's of us which uses OpenMP (Static, Intel OpenMP) Photoshop crashes (On OS X only). Have you ever encountered that?
Looking at the crash report it seems like though the first Plug In finished its task (Successfully) there are still threads under its name.
Well, after some similar issues with OpenMP + Intel 2017 (not all loops serializes, strange crashes and so on) I completely moved into Thread Building Blocks. It looks like more comfortable solution for me.
You can download source and compile static libraries for Windows for example. In case of OS X you can use already compiled dylibs directly with static switch in Xcode.
Unfortunately we don’t have a great story for how to do threading in third party plugins. The best answers I have (in order) are:
Use the platform tasking APIs (there are various people who’ve written little cross-platform shims around subsets of the platform threading) — GCD on Mac and the Windows Thread Pool on Windows.
Create raw OS threads using the native OS calls and either use those directly or put a simple tasking system on top of it (this is what Mondo does). In this model the plug-in creates a thread pool when the plug-in starts up and/or creates threads as needed, and tears them all down when it exits.
Use C++11 standard thread primitives. Safe on both Mac and Win, even for versions of Photoshop before we switched to the C++11 library. Drawback — their actual task creation behavior and performance are unpredictable and potentially suckful because “async” creates an OS thread per invocation on some platforms.
Use tbb. Note, however, that this ties you to specific versions of Photohsop. Because tbb is built as headers plus a DLL, the plug-in has its own copy of the headers and it’s using the tbb DLL that Photoshop ships. If the version of the headers that the plugin is built with aren’t compatible with the version of the DLL shipped with a particular version of Photoshop… bad things happen. There’s no good way to check AFAIK, and any update to Photoshop may bring an update to the TBB DLL. The good news is that Photoshop updates don’t *usually* break compatibility. But they might, meaning that a Photoshop update may require the third party to ship a new version of their plugin.
The behavior of all other thread/task packages (including OpenMP) invoked from plug-ins is unknown. Most of them have at least as bad an issue as TBB as described above, because thread / task packages all rely on a shared library to manage thread local storage and a single thread pool that’s shared across everything in a particular process. If the plug-in is shipping its own copy of a DLL that doesn’t come with Photoshop, it risks colliding with some other third party plug-in’s incompatible copy of that same DLL.
10
Replies
AdChoices