When we were first implementing this type of timeout on the /firefox/new/ page, we noticed occasional missed tracks in Chrome with values less than 500. Not saying that should be globally authoritative, but that's likely where the 500ms value came from.