I have a reproducible bug where OpenCV (454) hangs in cv::cvtColor, sometimes it get past it but instead hangs in cv::GaussianBlur operation instead. I have a really hard time to debug it but it looks like something happens in “parallel_for” execution in “smooth.simd.hpp” and finaly in “parallel.cpp” function “getCurrentParallelForAPI”.
example code / image to reproduce it ?
At the moment its not possible to link source code I can try to isolate it later. But I have noticed this output when I run debug build:
[ INFO:1] global c:\build\master_winpack-build-win64-vc15\opencv\modules\core\src\parallel\registry_parallel.impl.hpp (96) cv::parallel::ParallelBackendRegistry::ParallelBackendRegistry core(parallel): Enabled backends(3, sorted by priority): ONETBB(1000); TBB(990); OPENMP(980)
[ INFO:1] global c:\build\master_winpack-build-win64-vc15\opencv\modules\core\src\utils\plugin_loader.impl.hpp (67) cv::plugin::impl::DynamicLib::libraryLoad load C:\Alex\fb\opencv_core_parallel_onetbb454_64d.dll => FAILED
I have no folder named c:\build\master_winpack-build-win64-vc15\opencv !
Maybe I have not installed opencv correctly because that dll is missing in the installed opencv folder.
no, there is probably nothing wrong with your install.
those plugin dlls are optional, and not supplied here.
the info messages are also only shown in debug mode.
cout << getBuildInformation();
will show, which parallel support was builtin.
I have no folder named c:\build\master_winpack-build-win64-vc15\opencv !
this is from the machine, the libs were built on, not yours.