I experience smth like an infinite loop when a SchedulingContext object is destroyed. It seems the problem is that ThreadDispatcher::~ThreadDispatcher() called inside the destructor has a loop to finalize all jobs, but empty() always returns false, even if no jobs has been added at all.
I've tried only on Visual Studio. This behaviour is present e.g. in example 2_functions, when the program does what it should, but in the end does not really exit and gets stuck.
I experience smth like an infinite loop when a
SchedulingContext
object is destroyed. It seems the problem is thatThreadDispatcher::~ThreadDispatcher()
called inside the destructor has a loop to finalize all jobs, butempty()
always returnsfalse
, even if no jobs has been added at all.I've tried only on Visual Studio. This behaviour is present e.g. in example 2_functions, when the program does what it should, but in the end does not really exit and gets stuck.