More.
Tdrw on 706 crashed client,
at the exact same moment several team members' clients went down as well on different puzzles.
core.pack.interaction_graph.interaction_graph_factory: Instantiating DensePDInteractionGraph
core.pack.pack_rotamers: built 274 rotamers at 10 positions.
core.pack.pack_rotamers: IG: 119676 bytes
core.pack.interaction_graph.interaction_graph_factory: Instantiating DensePDInteractionGraph
core.pack.pack_rotamers: built 118 rotamers at 10 positions.
core.pack.pack_rotamers: IG: 29692 bytes
Unhandled exception in thread 02903608 (class game::application::novice::BoincThread): Error: database returned invalid result at time 1367103871 (......\rosetta_source\src\game\application\novice\boinc\Boinc.cc:479)
ERROR: Unhandled exception: Error: database returned invalid result at time 1367103871
ERROR:: Exit from: ......\rosetta_source\src\interactive\application\Thread.cc line: 210
ERROR: Rosetta exit unexpectedly
812 bytes
Reopened because of lots of crash reports.
lost one client in past hour, on 701, running my own version of Rav3n_pl GAB v0.6.1
also lost one client at same time as Murlow and several teammates ~2.5 hours ago, 701, TvdL DRW
win 7 64
most recent error in log:
Unhandled exception in thread 02C97E60 (class game::application::novice::BoincThread): Error: database returned invalid result at time 1367103807 (......\rosetta_source\src\game\application\novice\boinc\Boinc.cc:479)
ERROR: Unhandled exception: Error: database returned invalid result at time 1367103807
ERROR:: Exit from: ......\rosetta_source\src\interactive\application\Thread.cc line: 210
ERROR: Rosetta exit unexpectedly
Oops, Timo and I crossed and status went to done again. Changing to Ongoing and priority 1.
Changed it to open so it is visible on the list.
This isn't just windows, one of my mac clients has also crashed:
ERROR: Unhandled exception: Error: database returned invalid result at time 1367107230
ERROR:: Exit from: /Users/folditbuilder/foldit/mini-interactive-main-release/rosetta_source/xcode_4/../src/interactive/application/Thread.cc line: 210
ERROR: Rosetta exit unexpectedly
And, many are reporting crashes. It seems that there were a lot that crashed about the same time (just after 7pm EDT). There have been smaller groups of crashes and individual ones, also.
My crash was in a secondary (not a chat enabled) client.
Nuff said, as far as I can remember none of my crashes of 6-8 clients at a time have been on primary ( chat-enabled ) clients. I can only assume it's because I only very rarely do any processing on a chat-enabled client.
delta_score: -8.41838
Playing sound: 4
Error contacting server using URL: https://fold.it/portal/comm/whoami_csv
Error contacting server using URL: https://fold.it/portal/comm/whoami_csv
SRVR_THRD error: couldn't resolve host name: Error contacting server. (......\rosetta_source\src\game\application\novice\boinc\Boinc.cc:458)
Error contacting server using URL: https://fold.it/comm_cache/puzzle_user3_csv/994977_diff.txt
SRVR_THRD error: couldn't resolve host name: Error contacting server. (......\rosetta_source\src\game\application\novice\boinc\Boinc.cc:458)
Error contacting server using URL: https://fold.it/comm_cache/puzzle_group3_csv/994977_diff.txt
SRVR_THRD error: couldn't resolve host name: Error contacting server. (......\rosetta_source\src\game\application\novice\boinc\Boinc.cc:458)
Error contacting server using URL: https://fold.it/comm/foldit_ops
Unhandled exception in thread 02963608 (class game::application::novice::BoincThread): couldn't resolve host name: Error contacting server. (......\rosetta_source\src\game\application\novice\boinc\Boinc.cc:458)
ERROR: Unhandled exception: couldn't resolve host name: Error contacting server.
ERROR:: Exit from: ......\rosetta_source\src\interactive\application\Thread.cc line: 210
ERROR: Rosetta exit unexpectedly
All 3 clients went down overnight. This is becoming a daily routine.
I use only main especially to avoid these circumstances.
I'm starting to believe karstenw was on to something with his folding hiatus,
I won't keep playing like this.
Found the issue with the extra debugging information added. A fix for this issue will go out today.
Wonderful, thank you very much. =)
