Ha ha ha!!! So testing whether it is tracking right before turning tracking off...... That really looks like a timing bug!! They might even be able so spot it in the code if you tell them just that. Note that, in general, the test for tracking needs to be there because of some other misbehaving mount that I have long ago forgotten about (I can likely find it in the deep code tracking history but it is harmless so why bother?) or to simply avoid logging “(turning off tracking)” if the tracking is off already.

My question is how in the hell did you come up with removing that tracking test as a “shot in the dark”?????????