Anyone know how we’ve managed to get a crash on a pure virtual function call? Some kind of construction order problem maybe? Calling startTimer from a background thread?
I’m sure I once figured out how to do it but I’ve forgotten since! Any pointers appreciated.
+ 6831 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ (in CoreFoundation) + 17 [0x7fff38878d52] + 6831 juce::MessageQueue::runLoopSourceCallback(void*) (in App) + 129 [0x1044967c1] + 6831 juce::Timer::TimerThread::callTimers() (in App) + 233 [0x104495ca9] + 6831 __cxa_pure_virtual (in libc++abi.dylib) + 18 [0x7fff6fc15e92]
Maybe it’s deleting the object on a background thread. I can see that might do it.