If you manage to navigate away from the browser, good luck restoring the state.
Also why to spoil beautiful content by putting chrome (lowercase) around it?
Trying to cram everything in a single thread of execution seems like it would have been a mistake.
Though playing the demo with one eye on Task Manager shows only two processes (for the whole duration) - one hovering mostly around 50-60% CPU load, another at 0-5%.
Checking this with my CPU intensive demos, this looks like normal Chrome behavior (two processes, one with high load). New process seems to spawn only for new tabs.
So it doesn't seem like such optimization was used.