beta_helix Staff Lv 1
We are trying to diagnose why this is happening, but in the meantime please let us know if it happens again (discord is the fastest way to alert us) so we can get it back up and running.
Thanks again.
We are trying to diagnose why this is happening, but in the meantime please let us know if it happens again (discord is the fastest way to alert us) so we can get it back up and running.
Thanks again.
NBG here still.
Now seems ok.
Aaand now it's failed again.
Today failing again (Same on Windows 10 Pro)
It is unplayable :( :( :(
If i do not close the earlier opened foldit windows, i can use them, but no new window can be opened, because it crashes in few seconds(new install, other computer does not make any change). System Windows 10, laptop computer.
version: 1
{
"backtrace" : " 1: interactive::util::access_ptr::indirection_shim::indirection_shim +148 bytes (no line)\n 2: interactive::util::access_ptr::operator-> +20 bytes (no line)\n 3: game::util::IRC::event_numeric +1318 bytes (no line)\n 4: irc_strerror +4762 bytes (no line)\n 5: irc_process_select_descriptors +606 bytes (no line)\n 6: game::util::IRC::run +1082 bytes (no line)\n 7: game::application::IRCThread::operator() +836 bytes (no line)\n 8: interactive::util::Thread::thread_entry_func +69 bytes (no line)\n 9: interactive::util::Thread::win32_thread_startup_helper +14 bytes (no line)\n 10: BaseThreadInitThunk +25 bytes (no line)\n 11: RtlGetAppContainerNamedObjectPath +286 bytes (no line)\n 12: RtlGetAppContainerNamedObjectPath +238 bytes (no line)\n"
"build_id" : "20220222-22135083c0-win_x86"
"crash_id" : "91700c9a-c550-482c-b7b6-24ebbb5c4eb8"
"current_actions" : ""
"current_tool" : "Selection Interface"
"file" : "Unknown File:0"
"machine_id" : "3cf930ba-19d6-44b2-aeaf-5883a02fd140"
"macro_id" : "-1"
"message" : "Unknown Exception"
"player_id" : "1060747"
"puzzle_id" : "2012829"
"puzzle_running_time" : "23"
"running_time" : "1.3524e+06"
"timestamp" : "1646486801"
}
verify: b94484cb87d15adf96a51aa297f0aa46
It is crashing again on opening… on MacOS.
Weeeeeeeeeel, it's now up again, fingers crossed!
I'm using a Windows machine. After I finished puzzle 2114,
I quit all my Foldit clients, rebooted my machine, and then
restarted my Foldit clients without updating them. When I tried
to play puzzle 2116, they showed the starting structure and then
quit Foldit when I tried to do anything with it. Later, I tried
again, starting with puzzle 2108 or 2114 instead (both are
expired puzzles I had played before with Foldit). Puzzles 2108
& 2114 worked fine, so without quitting these clients, I switched
them to puzzle 2116. This time puzzle 2116 worked fine. Very
strange, but at least I can play puzzle 2116 now.