Pure 3019 settlement. In combat, 3 footmen vs a large stone golem. Lots of microing the combat, pause - take a step - pause. Usually when a hearthling runs away, the stone golem will pick an adjacent target. This time it didn’t. Thought that was odd. Then the game autosaved. Then I did something, and a moment later it crashed - I don’t recall if I issued an order, but I think the last act was unpausing; the crash wasn’t instant, it seemed like the game crashed while trying to figure out how to unpause and resume the world. As usual, no error message.
 Both crashes were the same basic circumstance. In the game, in combat, something goes wrong (I believe hearthling very recently died in both cases). Pause the game, ESC->load a recent save of the same world. Alt-tab to another window (Chrome browser). Game continues to load in the background. Eventually, roughly when I’d expect the load to complete, it crashes instead (as usual, application insta-closes, no error dialog or any such).
Starting Stonehearth up fresh, the same saves loaded in fine.
I’ve had other “crashes while loading a world while Stonehearth is not the focused application”, but these are the only two I thought to grab the crash dump for.
Versions and Mods:
Vanilla. 3019 I am sure was a pure world (ie generated in that version, no blueprints created in another version used). I believe the 3013s were also from pure worlds.
Windows 7 (x64), GTX 460 (768mb version), separate monitor. Stonehearth is being run in windowed mode, drag-to-top-of-screen-style maximized (hence how you get the odd 1920x1018 resolution - I presume the task bar eats the other 62 pixels).
Debated splitting this into two topics (3019, and 3013) vs one - two different game versions, different crash circumstances (though both in-combat), but not much context or detail or clues to give the posts any meat. Would be handy to know which you’d prefer.