Last year I submitted a bug regarding the use of ‘parallel_for_each’ and Windows Concurrency Library. We have found that when compiling in Visual Studio 2015 and 2017 with /MTd, the use of ‘concurrency::parallel_for_each’ can cause unhandled exceptions when the program is exiting.
After having some difficulty clarifying this issue with Microsoft I submitted the issue again this week and have found that they are aware of the problem. However, I’ve yet to be given any information on a timescale for a fix.
For our team this bug has caused problems when testing LLD. We suggest the removal of this MSVC specific functionality in “llvm::parallel” until a fix is made or alternative found. This could be easily swapped to use the existing standard library implementation in the meantime.
Thank you so much for tracking down such a tricky issue.
I agree that we should disable it. Should we just delete the ifdefs? We
could in theory disable it just for debug builds, but that could create
some hard to reproduce bugs.
Cheers,
Rafael
Owen Reynolds via llvm-dev <llvm-dev@lists.llvm.org> writes:
I personally haven’t seen the stability issue on my Windows machine, and looks like /MDd is passed to the command line for a debug build. I wonder how you would get a build with the /MTd option. Did you explicitly pass the option when you run CMake?
Unfortunately, it isn’t quite as simple as switching to the existing STL implementation as Owen suggested. The existing STL implementation is not entirely Windows friendly and can cause various crashes on exit too. We have some local patches to workaround these issues. I posted an “enhanced” Windows & Linux version of these local patches in https://reviews.llvm.org/D40366 as a potential solution to a crash on exit problem seen on Linux (see llvm-commits thread “std::detach() rarely crashes in Parallel.cpp”).
So to disable the use of PPL on Windows would require some changes to the existing STL implementation.
:detach() rarely crashes in Parallel.cpp”).