If you left a place within about fifteen seconds of it loading, the site threw an error. It hit around 1,100 sessions in two days, on phones and desktops alike.

The cause was an order of operations. When you leave, the scene shuts down the engine. The scene’s shutdown never told the streamed town to stop, so the town kept going after the engine was gone. Its timers fired at 2, 6 and 15 seconds, asked for a camera that no longer existed, and failed. That orphaned town also held on to its graphics memory.

The town is now destroyed before the engine. One more check sits after a wait where a shutdown could land in the middle. I could reproduce it in Chrome by opening Ludlow and navigating away three seconds later: two errors before the fix, none after.