1325 Thread 4 Crash

Started by actiasluna

actiasluna Lv 1

Second day on 1325 without touching Blueprint, and so far no crashes. FWIW.
Anecdotally, a player on a Windows box is having crashing problems with their 1325 as well.
Crashing when undoing last action a second time.

actiasluna Lv 1

And FYI I'm now running Sierra 10.12.2 (apparently machine updated after power loss yesterday) which might've introduced the new Thread 0 error which I don't remember having previously. Can't run foldit off my external any longer (which I put down to the update) either, which I could before the power outage.
Afterward, I ran DiskWarrior to be sure that the abrupt power loss hadn't scrambled the directories (it had done some things which DiskWarrior corrected).
So that's an additional variable (as if one was needed).

actiasluna Lv 1

More for the above thread 0 crash. When I reopened this second client, I noticed that I hadn't closed a cut. Once I closed the cut, mutate worked fine. (all of this on 1325 is being done completely without ever touching Blueprint, by the way.

actiasluna Lv 1

NOTE: With the current (not yet updated, October 2016) foldit build, without running Blueprint I have had only one crash on two open clients and that crash was on neither Threads 4 or 10. I've run recipes that were crashing with the Blueprint puzzles, none of them have crashed. In fact, the crash that occurred happened during ordinary hand work, when a cut was open and I mutated the shape. Don't know if this is significant, but here it is.

actiasluna Lv 1

Summing up: from Jan 8 to now (and to end of this puzzle's run) I'm working completely without Blueprint, with one Thread 0 crash during regular play on hand folding, working with the October Mac client, memory use "minimized" somewhat at first (when it looked like it was running stable I turned the Pulse when Working and Show All side chains buttons back on). Ran the usual recipes, without further incident after the first crash.