https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60966
--- Comment #19 from Jonathan Wakely <redi at gcc dot gnu.org> --- (In reply to Jonathan Wakely from comment #16) > The easiest fix is to call get_future() before passing the task into a new > thread, and store it in a std::vector<std::future<void>> Actually this only hides the error (by ensuring the shared state is not deleted because there is a future object still referring to it) but the fundamental problem with that code remains: You are calling the promise destructor before the call to set_value() completes. You are assuming that as soon as the shared state becomes ready the promise is no longer in use, but that's not true. After the shared state is made ready the rest of the set_value() function runs, which accesses members of the shared state. If you destroy the promise (and it has the only reference to the shared state) then it will destroy its members while they are still being used. This is a bug in your code, std::promise is like any other type: you must not delete it while another thread is still using it.
