Vladislav Shchapov

Reproduced in Github Actions! Commit with new actions: https://github.com/phprus/oneTBB/commit/eeb0154a8ca95e7ec12e5d4209225cb22195372e Branch: https://github.com/phprus/oneTBB/tree/msvc_vs_ci Test logs: https://github.com/phprus/oneTBB/runs/7818187404?check_suite_focus=true https://github.com/phprus/oneTBB/runs/7818187463?check_suite_focus=true

cc @pavelkumbrasev, @kboyarinov

@pavelkumbrasev, @isaevil, On win32: ``` [doctest] doctest version is "2.4.7" [doctest] run with "--help" for options =============================================================================== C:\tmp\oneTBB\test\tbb\test_collaborative_call_once.cpp(181): TEST CASE: only calls once - move only argument C:\tmp\oneTBB\test\tbb\test_collaborative_call_once.cpp(181): FATAL ERROR:...

@pavelkumbrasev, @isaevil, Commit 07415c5e0ad86a5fe5a20c647ef68145c1e5c8a0 from branch https://github.com/phprus/oneTBB/tree/msvc_vs_ci-1 (with new CI tasks for this issue). Error: ``` Exception thrown: read access violation. **ta** was 0x13EFD90. ``` Stacktrace: ``` tbb12.dll!tbb::detail::r1::task_arena_impl::initialize(tbb::detail::d1::task_arena_base & ta)...

@isaevil Hangs happen not only in Windows, but also in ubuntu (in github actions CI). When using Visual Studio 2019 (Win32) with LTO enabled, a hang or crash occurs on...

@isaevil You're right! This will not work in Win32. > In MSVC alignment requirements/promises only really apply to variables on the heap, not on the stack. Source: https://www.boost.org/doc/libs/1_80_0/libs/type_traits/doc/html/boost_typetraits/reference/aligned_storage.html What do...

Yes, only for MSVC. Unfortunately, LTO cannot be detected using predefined macros.

@isaevil , @pavelkumbrasev Commit with workaround: https://github.com/phprus/oneTBB/commit/d7055c53d601af8914dea0ef2ed1807b33fa907b All tests passed. Should I create an RR? Pre Requirement: #870 because the current build system sets the invalid working directory for tests.

Can you do a git bisect for your case? Or can you provide an example of the data on which the error occurs?

Fixed by #3043. Maybe close this issue?