After many "try and errors" ... it's not the call_repeatedly function itself. The threads created with call_repeatedly trying to access a singleton . Sometimes they can collide. Using threading.Lock() while accessing the singleton helps. The curious fact is, that the collision scenario never happend on the raspberry, but now on the Intel chipset.