There is now a protection on session history api, that will fail with "Too many calls to Location or History APIs within a short timeframe.", plus Bug 1891145 implemented an additional protection in global history, though it won't ever be perfect, as the risk of dropping real visits is high if we act too strictly. The bug as-is is no longer reproducible for me. Let's continue tracking Bug 1653041 for further improvements on the history flooding matter.
Bug 1491452 Comment 8 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
There is now a protection on session history api, that will fail with "Too many calls to Location or History APIs within a short timeframe.", plus Bug 1891145 implemented an additional protection in global history, though it won't ever be perfect, as the risk of dropping real visits is high if we act too strictly. The bug as-is is no longer reproducible for me. Let's continue tracking Bug 661590 for further improvements on the history flooding matter.