As the saying goes, "be careful what you wish for, you might get it".
After getting the new beta 8.1.16 with the fix to error #127, a couple times I've found my computer stuck in an infinite cycle of restarting a CPU work unit when it aborts due to a guru meditation error. It restarts, immediately fails, restarts again, immediately fails again, and so on. The most recent iteration started sometime Thursday evening, I didn't catch it until early Sunday morning after it generated over 125MB of log files.
There should probably be an upper limit on the number of times it restarts a work unit after which it pulls the rip cord 🪂.
As the saying goes, "be careful what you wish for, you might get it".
After getting the new beta 8.1.16 with the fix to error #127, a couple times I've found my computer stuck in an infinite cycle of restarting a CPU work unit when it aborts due to a guru meditation error. It restarts, immediately fails, restarts again, immediately fails again, and so on. The most recent iteration started sometime Thursday evening, I didn't catch it until early Sunday morning after it generated over 125MB of log files.
There should probably be an upper limit on the number of times it restarts a work unit after which it pulls the rip cord 🪂.
A snippet of one of the log files showing the error & restart.
``` *********************** Log Started 2023-03-17T00:00:00Z *********************** 00:00:00:I1::WU1098:*********************** Log Started 2023-03-16T23:59:59Z *********************** 00:00:00:I1::WU1098:************************** Gromacs Folding@home Core *************************** 00:00:00:I1::WU1098: Core: Gromacs 00:00:00:I1::WU1098: Type: 0xa8 00:00:00:I1::WU1098: Version: 0.0.12 00:00:00:I1::WU1098: Author: Joseph Coffland