Update 4.1 | 0.8.5 (b598)

I'm working on reproduction right now, but I happened to save the game shortly before the crash happened. If you load the world and let it run for ~30s, an alert will appear about something running low on copper. It crashed during the pan from clicking on that. The other actions I took between save & alert shouldn't factor in, but that's what I'm testing right now.

Retried the crash sequence and a crash did not occur. Was it a memory state or something? System memory loading isn't nearly enough to have caused that (~50% of 32GB), and while GPU memory loading is sitting pretty at "Considerable", there were no signs of a graphics crash.

That said, the style of crash prettymuch matched that one crossover crash- the game froze, sound still playing, for a few seconds, then finally crashed (the Unity crash dialog popped up, the game actually cut a few seconds after that). Didn't take the system with it, though; the cursor still moved, though the game didn't respond to the motion, and no apparent effect on the rest of the system, both during the freeze and after the crash.

Windows.