Partially, though my observations suggest a x40 specific issue related to dynamic routing when it appears you are off course and is trying to correct. It could be related to internal map data or firmware.
If it was due to “internal map data”, the route line should show it. It’s almost certainly not that. The older units had a limit to how long a route they could compute. Much, much shorter than 9,000 miles. I suspect the newer units have a similar limit.
9,000 miles is a ridiculously large number to be off by. I suspect the device is losing track of your location and using 0, 0 instead.
Again, I've seen it on 540 and not 1030 so this may be a device specific glitch.
Never saw it in a 800, 1030, or 1030+. I don’t recall seeing this issue reported for any of the units (including the *40 line) in the Garmin forums. There’s no indication that it’s a general issue across all of the devices. If it’s an issue in recent firmware for the *40 line, that might explain the lack of reports about it.
It is more of a curiosity to me than a serious issue since I have two devices, generally know where I am headed and the problem disappears once the device is back in a state where you are back on course (sometimes easy if I intentionally detoured to a store, a little tougher when there is a closure and I'm rerouting without the device).
It’s not a serious issue. 2ering’s histrionics doesn’t make it so either.
You shouldn’t need another device to have some sense how much more you need to go. One can even look at the map to get an idea of how much extra the detour will be.
Obviously, these sorts of problems shouldn’t happen. But, if they happen, it’s better they fail in an obvious way.