timerExists assert hit in ~Timer() when destroyed from DeletedAtShutdown about juce HOT 2 CLOSED

Surely the only way to make that happen is if you start a timer in the destructor of your DeletedAtShutdown object!

There are infinitely many ways in which carelessness inside destructors of objects during shutdown can cause havoc, which is why you always need to be specially careful there. I don't think this case is particularly deserving of any kind of workaround to avoid the assertion - you just need to not go creating timers (or anything else!) while objects are being destroyed!

from juce.

It is possible for another thread which hasn't been stopped yet to call startTimer() under normal operation causing the Timer::TimerThead to be recreated. Surely Timer::TimerThead should not be able to be deleted while there are active Timer objects with Timers running.

from juce.