I've seen at least three cases on Recipe Death Syndrome (RDS) in the last couple of days.
In cases of RDS, the normal "active recipe" window that shows the recipe name disappears. Usually this happens when a recipe completes. The stop/timer overlay is still displayed in the lower left corner, but grayed out. The client is no longer responsive to any keys or clicks.
The scriptlog for the recipe that was running shows no sign of a recipe ending.
The only solution seems to be to close the client. This doesn't cause a crash. After the close, log.txt doesn't contain anything meaningful. In the one case I examined closely, log.txt hadn't been written for several hours, so it's possible that buffered lines were lost by closing the client.
I think I've seen RDS before, but not recently. Perhaps it's somehow related to server timeouts. The server seems to have been slower than usual the past couple of days. Maybe something to do with uploading timed saves is gumming up the works, but that's just speculation.
The only suggestion is to look at increasing the frequency for flushing log.txt to disk, just in case there's something diagnostic in there.
I had another case of RDS just now. I was left with the window shown below. The stop/timer icon is in the lower left corner, but it doesn't respond to clicks. I found the UI is not completely dead however. I was able to open the cookbook, and tried running another recipe. This did nothing but clear the scriptlog window. I gave up at that point and just closed the client.
The scriptlog file contains the end tags, as though the recipe ended normally. In this case, it's only acid tweaked 91 out of 263 segments, so it wasn't nearly done. Also, the recipe has a cleanup routine that always print several lines at the end, and there's no path in the code that exits without going through cleanup.
I'll do a more careful analysis the next time this happens. It seems to be a regular feature now, so I expect to see it again.
I had another similar one. Most of the menus are available. The home key brought the protein back on screen. It had a selected segment. It wasn't possible to clear the selection or select more segments. I used the escape key to open the main menu. There didn't seem to be much else to do, so I used "Save and Exit", which worked.
The log.txt file is attached.
log.txt
Here's the screen for the one in the previous post. Again, the stop button in the lower left can't be clicked, but the animated segments continue to revolve around it. The scriptlog again contained the closing tags.
I'd say the recipe is only half dead, but there doesn't seem to be a way to get Foldit to release and move on to something else.
It's not clear when the problem hit, but it seems like several hours went by, based on the amount of work completed.
I can confirm I have seen several cases like these in previous (Windows) clients as well. Running Windows 7.
I attributed them to bugs in the client but as I had no further information I did not file a feedback report on it.
The client could be gracefully closed, but not much more than that. The 'Clock' was indeed greyed and could not be stopped. Maybe that is also a hint as to where it fails if there is a clock update, a call to code and then again a clock update. I could imagine it hangs inbetween the clock updates.
It is indeed a mystery. I think the cases of RDS I observed were all while running a recipe in the "V2 Acid Tweaker R v1.x" family, but I'm not sure.
Perhaps the problem is something to do with switching rotamers. I seem to recall issues with that from the past.
At any rate, nothing a recipe does should produce an effect like RDS.
I often see this RDS with latest ED puzzle (2460).
Nothing happens, no points won for an infinite time.
The only way I found is to close the window and start over.
I just saw another case of RDS, this time on revisiting puzzle 2459, running Band Worm Pairs Infinite Filter. That rules out puzzle size as a factor, only 64 segments on 2459.
Thanks for this update, LociOiling.
Has RDS always happened with multiple clients running, or have any of you seen it running only a single client?
same issue with Win11 Foldit Release 35 Main, only one client is running with puzzle 2461 using recipe Ligand Docker v2.5
