3 ms·
It's not deterministic because you don't know the timing relationship between threads which may drop references. The only sense in which it is deterministic is
by PaulDavisThe1st 6y ago
It's not deterministic because you don't know the timing relationship between threads which may drop references. The only sense in which it is deterministic is that "when the reference count reaches zero, the object will be destroyed". That's a long way from the determinism of manual/explicit memory management. It gets even worse if there are per-thread pools in use, though to be fair, this is mostly an application design issue rather than a language one.