I'm running Puzzle 1659b on 2 new devprev clients on a Dell Inspiron intel CORE i5 laptop.
These clients have crashed several times so far. Below are 2 example log.txt files from
the same recipe run with slightly different input parameters and starting structures.
If you need more information, please send me a Foldit e-mail.
Thanks!
Here are the 2 log files mentioned above:
More logs from the same recipe on the same 2 clients
but more different starting structures & input parameters:
Log.txt files
Another crash log from same client but a different recipe & starting structure:
Thanks for the crash logs!
We're especially interested in specific actions that cause a crash. I know this can be difficult to tell when the crash happens in the middle of a recipe—but if you encounter a crash while using a tool (like the Rama Map, or simply Pulling on the protein), please let us know! Especially if you can reproduce the crash more than once!
Rebuid and ReMix are not working on 1659b in the new DevPrev.
Problem signature:
Problem Event Name: APPCRASH
Application Name: Foldit.exe
Application Version: 0.0.0.0
Application Timestamp: 546d537b
Fault Module Name: KERNELBASE.dll
Fault Module Version: 6.1.7601.23807
Fault Module Timestamp: 5915f98e
Exception Code: e06d7363
Exception Offset: 0000c54f
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1043
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789
From log.txt:
SRVR_THRD getting notifications…
Time: 378985 - Tool on_action_complete called
***** STARTING THREAD ActionGlobalMinimize
RT: 11111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111
core.kinematics.AtomTree: [ ERROR ] No proper DoF can be found for these four atoms: 466-1, 466-2, 466-3, 467-1!
core.kinematics.AtomTree: [ ERROR ] No proper DoF can be found for these four atoms: 466-2, 466-3, 467-1, 467-2!
core.kinematics.AtomTree: [ ERROR ] No proper DoF can be found for these four atoms: 475-3, 476-1, 476-2, 476-3!
core.kinematics.AtomTree: [ ERROR ] No proper DoF can be found for these four atoms: 466-1, 466-2, 466-3, 467-1!
core.kinematics.AtomTree: [ ERROR ] No proper DoF can be found for these four atoms: 466-2, 466-3, 467-1, 467-2!
core.kinematics.AtomTree: [ ERROR ] No proper DoF can be found for these four atoms: 466-3, 467-1, 467-2, 467-3!
core.kinematics.AtomTree: [ ERROR ] No proper DoF can be found for these four atoms: 475-1, 475-2, 475-3, 476-1!
core.kinematics.AtomTree: [ ERROR ] No proper DoF can be found for these four atoms: 475-2, 475-3, 476-1, 476-2!
core.kinematics.AtomTree: [ ERROR ] No proper DoF can be found for these four atoms: 475-3, 476-1, 476-2, 476-3!
Sending SOPs:
Sending SOPs:
core.kinematics.AtomTree: [ ERROR ] No proper DoF can be found for these four atoms: 466-1, 466-2, 466-3, 467-1!
core.kinematics.AtomTree: [ ERROR ] No proper DoF can be found for these four atoms: 466-2, 466-3, 467-1, 467-2!
core.kinematics.AtomTree: [ ERROR ] No proper DoF can be found for these four atoms: 475-3, 476-1, 476-2, 476-3!
core.kinematics.AtomTree: [ ERROR ] No proper DoF can be found for these four atoms: 466-1, 466-2, 466-3, 467-1!
core.kinematics.AtomTree: [ ERROR ] No proper DoF can be found for these four atoms: 466-2, 466-3, 467-1, 467-2!
core.kinematics.AtomTree: [ ERROR ] No proper DoF can be found for these four atoms: 466-3, 467-1, 467-2, 467-3!
core.kinematics.AtomTree: [ ERROR ] No proper DoF can be found for these four atoms: 475-1, 475-2, 475-3, 476-1!
core.kinematics.AtomTree: [ ERROR ] No proper DoF can be found for these four atoms: 475-2, 475-3, 476-1, 476-2!
core.kinematics.AtomTree: [ ERROR ] No proper DoF can be found for these four atoms: 475-3, 476-1, 476-2, 476-3!
UNHANDLED EXCEPTION
1: RaiseException +88 bytes (no line)
2: no symbol (no line)
3: no symbol (no line)
4: no symbol (no line)
5: no symbol (no line)
6: no symbol (no line)
7: no symbol (no line)
8: no symbol (no line)
9: no symbol (no line)
10: no symbol (no line)
11: no symbol (no line)
12: no symbol (no line)
13: no symbol (no line)
14: no symbol (no line)
15: no symbol (no line)
16: BaseThreadInitThunk +18 bytes (no line)
17: RtlInitializeExceptionChain +99 bytes (no line)
18: RtlInitializeExceptionChain +54 bytes (no line)
Latest devprev client (with the announced fixes)
Solution shared as "doferror_BP".
I saw one of these "no symbol (no line)" crashes overnight running a remix recipe on 16b9b. Overall, only a couple of crashes, not the repeated crashes others are reporting. Unfortunately, I restarted the client before saving the log file.
I do see these "no proper DoF" messages in log.txt, even without a crash. They involve the permanent cutpoints in the designable section, at segments 466-467 and 475-476 in my solution.
From previous discussions, I think the "no proper DoF" lines come from Rosetta, so there's probably not a direct fix in Foldit. Maybe something happens that clobbers a little memory for each of these messages, eventually leading to a crash.
As discussed in #veteran, the crashes in EDRW and DRemix are just a recipe issue.
The problem is the variable "clrdonelistgain", which is set to the segment count early on.
In 1659b, there can be over 500 segments.
In the "more options" dialog, "clrdonelistgain" is used in a slider with max value of 500.
The result is a recipe crash, at line 1532 in EDRW 3.0.2, when the segment count is over 500.
The solution is to set clrdonelistgain to a constant like 250 (anything less than 500).
In EDRW 3.0.2, line 1863 is the spot.
I'd suggest exporting the recipe and using a good editor like Notepad++ that shows line numbers
to make the change.
I've also messaged Timo about the problem.