miscellaneous crashes, hard to reproduce.
|Opened on:||Monday, November 26, 2018 - 19:55|
|Last modified:||Monday, October 28, 2019 - 20:23|
Since the summer 2018 updates, there seems to be a new set of crashes. The exact causes aren't clear, but they seem to strike more often during hand folding than when running a recipe. Some times moving a section with open cutpoints has caused a crash, sometimes just pulling on part of the protein is enough.
Under current versions of Windows 10, crashes cause the client to just disappear. The Foldit window closes without any additional dialog.
Use this feedback to add your crash. Tell us what you were doing when the crash occurred, including which puzzle you were working on, your wiggle power setting, and at least the general type of recipe you were using, if any.
Collecting some additional debugging information will help.
When a crash occurs, you'll often see one or more sets of "Unhandled Exception" messages in the Foldit log file, log.txt. The log file gets overwritten when you restart Foldit, so check it before restarting the client. The log file is located in c:\Foldit or wherever you've installed Foldit, so c:\Foldit\log.txt would be its typical path.
You can attach the complete log.txt to your feedback entry, or just copy the unhandled exception lines (using Notepad or the equivalent) and pasting them here.
Another possible source of information is debug.txt, which sometimes gets generated during a crash. This file summarizes the crash information. In theory, debug.txt is automatically sent to the Foldit server when you restart. In practice, most of the recent crashes don't seem to generate a debug.txt file. If you have a debug.txt, attach it to your posting. Be sure the debug.txt was from the most recent crash, since these files don't get deleted, and only get overwritten when there's a suitable crash.