Fix lifetime issues for barriers captured by reference

We have instances in unit-tests, where we create a barrier, create a lambda that captures the barrier by reference, and then move the lambda to be executed by a separate thread (e.g., this one). In some cases, the barrier can go out of scope and freed, while the other thread is yet to finish the execution of the lambda. This incidents could sporadically cause access violation failures in unit-tests.