Re above: happened again. So crash occurs as soon as close the manage solutions box. Same log as above.
No object matching key 0.
hotkey pressed 1 times Ctrl+O
Sending SOPs:
Sending SOPs:
Sending SOPs:
Generated 15 rotamers for LG_50023 in 1.023s total.
UNHANDLED EXCEPTION
1: alIsAuxiliaryEffectSlot +598376 bytes (no line)
2: alIsAuxiliaryEffectSlot +598984 bytes (no line)
3: library_main +5297766 bytes (no line)
4: library_main +5297955 bytes (no line)
5: library_main +371112 bytes (no line)
6: library_main +3400005 bytes (no line)
7: library_main +3400443 bytes (no line)
8: BaseThreadInitThunk +36 bytes (no line)
9: RtlValidSecurityDescriptor +448 bytes (no line)
10: RtlValidSecurityDescriptor +400 bytes (no line)
What Madde and I noticed: in devprev it 'usually' crashed when you share and and usually crashes the first time you open a share.
Tried reinstalling fold it client - did not fix issue
I just updated a client and started 1519 in it.
I tried downloading group-shared solutions from
the server with it. I'd download 1-2 solutions
and then the client would quit. This happened
multiple times.
Clicked to change atom. Crash.
signed Residue: [H]Oc1c(-c2c([H])c(C(N([H])C3([H])C([H])([H])C([H])([H])C([H])([H])C([H])([H])C3([H])[H])=N+[H])c([H])c([H])c2[H])n(N+C([H])([H])[H])c(N+C([H])([H])[H])c1C(C([H])([H])[H])(C([H])([H])[H])N+([H])[H]
FinalE finalize:
core.chemical.ResidueTypeSet: [ WARNING ] ResidueType LG_50024 of mode fa_standard is being added to a ResidueTypeSet of mode centroid
replacing residue
Tool on_action_complete called
Tool on_action_complete called
Tool on_action_complete called
Designed Residue: [H]Oc1c(-c2c([H])c(C(N([H])C3([H])C([H])([H])C([H])([H])C([H])([H])C([H])([H])C3([H])[H])=N+[H])c([H])c([H])c2[H])n(N+[O-])c(N+C([H])([H])[H])c1C(C([H])([H])[H])(C([H])([H])[H])N+([H])[H]
FinalE finalize:
core.chemical.ResidueTypeSet: [ WARNING ] ResidueType LG_50025 of mode fa_standard is being added to a ResidueTypeSet of mode centroid
replacing residue
Tool on_action_complete called
Tool on_action_complete called
Generated 20 rotamers for LG_50024 in 8.507s total.
UNHANDLED EXCEPTION
1: alIsAuxiliaryEffectSlot +598376 bytes (no line)
2: alIsAuxiliaryEffectSlot +598984 bytes (no line)
3: library_main +5297766 bytes (no line)
4: library_main +5297955 bytes (no line)
5: library_main +371112 bytes (no line)
6: library_main +3400005 bytes (no line)
7: library_main +3400443 bytes (no line)
8: BaseThreadInitThunk +36 bytes (no line)
9: RtlValidSecurityDescriptor +448 bytes (no line)
10: RtlValidSecurityDescriptor +400 bytes (no line)
An update on these crashes: I think I've tracked down the issue.
For those interested in the technicalities, the code doing the "Generated NN rotamers …" output is in a sub-thread, and when loading a new solution there's a chance this thread can stick around past the point where it's needed. It then tries to access data from the previous puzzle state - which is now missing - resulting in the crash.
I've updated the developer's internal version to make sure this doesn't happen. This may take a bit of time to work its way to devprev and main, though. Until then, you can work around the crashes by waiting a sufficient amount of time after changing the chemical structure of the ligand before loading a new solution. (Unfortunately "sufficient" depends on the chemical type. Normally 30s or so should be more than enough, but sometimes it will take more time.)
I apologize for the issues, and thanks for your efforts in troubleshooting it. Your detailed description of the issue helped me narrow down the problem.
Not sure if it's the same issue, but I also get a crash when editing the description of a saved solution.
And a crash when attempting to upload a solution, but the upload fails due to too many
solutions already uploaded.
And a crash when downloading (not opening) a shared solution.
When sharing to group, it crashes but it's shared.
When loading the first time, it crashes but it's loaded on local.
When loading from client, it's ok.
Then, after some manual hand fold (adding atoms), and Undos several times, it crashes again and you have to start the all process again (loading first time etc).
seeing references to this in log.txt (seems like missing dictionary file):
Finished show_puzzle_screen…
has key .opdb
Loading restype LG_5008 (LIG,Z) from SMILES string [H]OC([H])(C([H])([H])[H])C([H])([H])[H]
core.chemical.GlobalResidueTypeSet: [ WARNING ] PDB component dictionary file not found at (./)[chemical/pdb_components/components.Nov01_2017.A_to_C.cif, chemical/pdb_components/components.Nov01_2017.D_to_Z.cif]
core.chemical.GlobalResidueTypeSet: [ WARNING ] or in the Rosetta database
core.chemical.GlobalResidueTypeSet: [ WARNING ] For more information on how to obtain the file and set it for use with Rosetta, visit:
https://www.rosettacommons.org/docs/latest/build_documentation/Build-Documentation#setting-up-rosetta-3_obtaining-additional-files_pdb-chemical-components-dictionary
core.chemical.GlobalResidueTypeSet: [ WARNING ] If you want a quick fix, you can try to directly ftp in the file:
core.chemical.GlobalResidueTypeSet: [ WARNING ] ftp -o cmp-database-b22abac3dbaea02a314dc8f75ee1bf09\database\chemical/components.cif.gz ftp://ftp.wwpdb.org/pub/pdb/data/monomers/components.cif.gz
core.chemical.GlobalResidueTypeSet: [ WARNING ] and then add to your Rosetta command-line: -PDB_components_file chemical/components.cif.gz Could not find: 'LIG' in pdb components files [chemical/pdb_components/components.Nov01_2017.A_to_C.cif, chemical/pdb_components/components.Nov01_2017.D_to_Z.cif]! Skipping residue…
core.chemical.GlobalResidueTypeSet: [ WARNING ] Could not find: 'LIG' in pdb components files [chemical/pdb_components/components.Nov01_2017.A_to_C.cif, chemical/pdb_components/components.Nov01_2017.D_to_Z.cif]! Skipping residue…
has key .opuzzle_setup
has key .ofilters
has key .osmiles_queue
starting score : -432.038
puzzle loaded
Sorry about these warning messages – the dictionary it's complaining about shouldn't be present in Foldit (it's big and unused), but a setting to skip looking at it was missed. It shouldn't affect the puzzle though.
The next update should include an update to the settings such that these messages will no longer get printed.
