crashed when trying to change puzzle

Case number:845829-2004970
Topic:Crash/Hang
Opened by:alcor29
Status:Open
Type:Bug
Opened on:Wednesday, April 4, 2018 - 21:47
Last modified:Saturday, April 7, 2018 - 20:51

Main, original UI, Win10/64

Log when trying to change puzzle to 1504

hotkey pressed 1 times Ctrl+P
Sending SOPs:

Sending SOPs:

Sending SOPs:

downloading: http://fold.it/portal/files/puzzle_pdb/puzzle_post_1575.zip
has key .ocmdline
has key .roscript
TASKOPERATIONS
SCOREFXNS
FILTERS
MOVERS
APPLY_TO_POSE
PROTOCOLS
has key .owts
has key .opdb
core.conformation.Conformation: [ WARNING ] missing heavyatom: OXT on residue ILE:CtermProteinFull 85
has key .opuzzle_setup
has key .ofilters
starting score : 17656.1
puzzle loaded

ERROR: Error in core::conformation::Conformation::residue(): The sequence position requested was greater than the number of residues in the pose.
ERROR:: Exit from: c:\cygwin64\home\jflat06\foldit\develop\source\src\core/conformation/Conformation.hh line: 500

UNHANDLED EXCEPTION
1: RaiseException +98 bytes (no line)
2: alIsAuxiliaryEffectSlot +603490 bytes (no line)
3: library_main +47188928 bytes (no line)
4: library_main +3802269 bytes (no line)
5: library_main +5548228 bytes (no line)
6: library_main +4006073 bytes (no line)
7: library_main +4196897 bytes (no line)
8: library_main +4157542 bytes (no line)
9: library_main +3911140 bytes (no line)
10: library_main +3320935 bytes (no line)
11: library_main +1887804 bytes (no line)
12: library_main +5349881 bytes (no line)
13: library_main +4168376 bytes (no line)
14: library_main +2127354 bytes (no line)
15: library_main +2157592 bytes (no line)
16: library_main +214434 bytes (no line)
17: library_main +105548 bytes (no line)
18: library_main +157219 bytes (no line)
19: library_main +370360 bytes (no line)
20: library_main +858148 bytes (no line)
21: library_main +370360 bytes (no line)
22: library_main +3390229 bytes (no line)
23: library_main +3391402 bytes (no line)
24: library_main +3641166 bytes (no line)
25: library_main +3435791 bytes (no line)
26: library_main +5162539 bytes (no line)
27: library_main +370360 bytes (no line)
28: library_main +3434972 bytes (no line)
29: library_main +5167379 bytes (no line)
30: library_main +5157375 bytes (no line)
31: AddClipboardFormatListener +75 bytes (no line)
32: EndTask +33897 bytes (no line)
33: EndTask +44389 bytes (no line)
34: EndTask +32602 bytes (no line)
35: CallWindowProcW +27 bytes (no line)
36: glDebugEntry +3651 bytes (no line)
37: AddClipboardFormatListener +75 bytes (no line)
38: EndTask +33897 bytes (no line)
39: EndTask +44389 bytes (no line)
40: DispatchMessageW +1228 bytes (no line)
41: DispatchMessageA +16 bytes (no line)
42: library_main +5165722 bytes (no line)
43: library_main +3192489 bytes (no line)
44: library_main +13065 bytes (no line)
45: library_main +21 bytes (no line)
46: no symbol (no line)
47: no symbol (no line)
48: no symbol (no line)
49: BaseThreadInitThunk +36 bytes (no line)
...

(Wed, 04/04/2018 - 21:47  |  3 comments)


Joined: 09/21/2011
Groups: Void Crushers

Question: does restarting and going to that puzzle also crash?
If not, my suggestion to the developpers is that somehow the nr of residues is not reinitialized when loading a puzzle from another one,
Are you running on MacOS? This looks really like the same error as in loading a share problem.

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

Hey, Timo. No, restart doesn't crash. Running Win10/64. Original UI, Main.

LociOiling's picture
User offline. Last seen 59 min 4 sec ago. Offline
Joined: 12/27/2012
Groups: Beta Folders

Crashes when changing puzzles are pretty common on Windows. It's been that way for a long time. For design puzzles, you sometimes you get a crash when loading a solution, due to a similar segment count issue.

Smilingone long ago advised restarting when changing puzzles and even when changing recipes. Certainly after a long run of EDRW, it's time for a new client. On Windows, Foldit has a known "handle leak", and who knows what else isn't getting cleaned up.

See these "handle leak" feedbacks:

https://fold.it/portal/node/2002316
https://fold.it/portal/node/2004487

Leaked handles aren't a big deal usually, but they show why frequent restarts are not a bad idea.

Sitemap

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, RosettaCommons