"Mono Lake, CA" causes an error during the initial calculations. Probably has to do with starting right on a stopping feature. Needs to either resolve or tell the user there's been an error and reset. #1
Was undersampling coordinates for very short paths and ending up with invalid paths. Fixed the issue and now even ridiculously short paths should render correctly and not error out.
Getting the same issue with "Vermilion, Ohio" in search bar. Console error at same point.