Can a basic problem be eliminated?

Case number:845829-2004365
Opened by:alcor29
Opened on:Sunday, October 22, 2017 - 18:59
Last modified:Friday, October 27, 2017 - 21:31

Many freezes and crashes are simply caused by clicking on one action, either impatiently or absentmindedly, while another action is in progress. I always assumed the fix is: don't do that buddy. I wonder however, if there is any programming solution to that, for example: If an action is in progress ignore all other stipulated selections. (Some selections can still be allowed).?

(Sun, 10/22/2017 - 18:59  |  3 comments)

LociOiling's picture
User offline. Last seen 6 hours 56 min ago. Offline
Joined: 12/27/2012

The most common crash I get is when switching puzzles. The moral of that story is to always start a new client before starting a new puzzle. Also, re-starting a client between long-running recipes is a good thing. Bletchley Park discovered a major "handle leak" on Windows a while back that's still with us.

I don't recall any recent problems with different combinations of actions. Do you have something that's repeatable? Also, it might help to know which OS and maybe machine specs.

alcor29's picture
User offline. Last seen 19 min 35 sec ago. Offline
Joined: 11/16/2012

Win10/64; Quad core AMD 2.2ghz.

As I mentioned I always ignore these because I assume I shouldn't have clicked on the action before another one was finished or I shouldn't have done ctrl+O twice, etc. I should think this is a very common and universal occurrence, but next time it happens I will post the log if it helps.

alcor29's picture
User offline. Last seen 19 min 35 sec ago. Offline
Joined: 11/16/2012

Also this occurs in main. (I rarely use devprev).


Developed by: UW Center for Game Science, UW Institute for Protein Design, Northeastern University, Vanderbilt University Meiler Lab, UC Davis
Supported by: DARPA, NSF, NIH, HHMI, Amazon, Microsoft, Adobe, Boehringer Ingelheim, RosettaCommons