Chrome on iOS is all smoke and mirrors, Apple does not allow other browsers other than Safari, so Google just wraps the Safari engine with Google specific services (like accounts and syncing). In fact, until iOS8, this also introduced a significant performance issue.
So what you are actually seeing is Safari crashing and then deciding to automatically reload the page only to crash again, rinse, and repeat. If I had to guess, I would say it’s the Seattle streets data causing the issue, since it’s a large GeoJSON data set and Safari in general is a terrible browser that can’t handle it. Even running it on desktop Safari appears to have issues.
So long story short, there’s nothing you can do on your end to make it work. The app itself needs to detect Safari and disable features that Safari can’t handle (for instance, by disabling street data).
Safari is the bane of every web developer’s existence and almost every non-trivial app needs to be babied to work on it, as we continue to improve streaming vector data support in Cesium, this particular problem will be significantly lessened for apps showing a lot of data, but brute forcing it (like the streets data is doing) will continue to be an issue unless Apple decides to start improving Safari.