>> But perhaps you’ve defined your own subclass of “BasicTaskScheduler0”, and
>> are declaring an object of that subclass statically??
Yeah it’s a subclass of BasicTaskScheduler0, which (through many feet of
abstraction) was getting initialized statically. In the subclass I have the
mechanic
> On Aug 12, 2015, at 6:59 PM, Jeremiah Morrill
> wrote:
>
> I’ve come across an issue where a BasicTaskScheduler0 gets statically
> initialized (ran before main(…))
I don’t see how this can be happening with the code that we’ve supplied,
because the “BasicTaskScheduler0” constructor is prot
I’ve come across an issue where a BasicTaskScheduler0 gets statically
initialized (ran before main(…)) and the DelayQueue gets stuck in an infinite
loop.
I’ve found that the problem is in DelayQueue.cpp in the constructor of
DelayQueue.
DelayQueue::DelayQueue()
: DelayQueueEntry(ETERNIT
