Earlier quoted context omitted.
> at least show a sensible error message so people who haven't spent ridiculous amounts of time reading the source code of your product as part of their job can troubleshoot their systems. Not "something failed, go read logcat, maybe it helps, good luck". While I’m not sure whether it’s true, I think the reasoning behind this is that to the average user, a sensible error message is about as useful as "something faile…
They could at least google it and find out how someone else solved the same problem. No such luck with more generalized error messages.
In this sort of scenario the better choice rather than implementing error detection is just fixing the original problem that caused an infinite loop so users don't need to fix anything in the first place. I think the reason why debugging/resolving issues seems so complicated in modern times is in part because we already did fix most/all the "easy" issues from the past generation -- the only remaining issues are extremely hard to catch or, in the case of the Halting Problem you experienced, mathematically impossible.