Tried opening and crashed. Tried again and crashed. Running Windows 10.
It took me 5 attempts to load the puzzle
opens on mac os x: crashes when trying to open on linux/wine. Main versions
I and some others are getting this message when trying to load 1221:
"A timeout was reached due to excessive server load. Sorry for the inconvenience, please try again later."
Win 7 devprev
By checking "disable network timeouts" on the login screen, I was able to get this puzzle open.
I'd love to hear the explanation of why that is, but good enough for now.
Not sure if there's a good reason to leave "disable network timeouts" unchecked. Having it unchecked did not prevent clients from hanging after the most recent server outage.
The description for this puzzle is very poor. What is the deal with the scattered, partial hydrophobes seemingly unattached to any protein yet they have unique segment numbers? The ease with which it crashes makes it unworkable.
Yes, in addition to protein, this crystal structure does include some well-ordered small molecules. The small spheres represent Zn atoms, and the ringed molecules are imidazole (which is very similar to the side chain of histidine). These small molecules occupy strong density in the electron density map, but they are frozen in place, and can mostly be ignored in this puzzle.
No comments as reported by some. Simply crashes while trying to open.
win 7 main client - just stays stuck on Loading screen
Checking "disable network timeouts" on the login screen let it download without the timeout message.
Even with no scripts running, the 1221 client is using nearly twice the memory of a client with EDRW running on puzzle 1220. Check your memory usage on the performance tab of task manager, anything above 90% might be an issue.
While loading it briefly peaked to 1.4 Gigabyte, while running it uses around 920 Megabyte.
But then it crashes into a grinding halt
Same here: disabling network timeouts prevents the server timeout message, but the game loads the 1221 score boards (can't tell if it loads the protein, as I can't see the protein on the screen) and then promptly crashes. Win 7 devprev.
Also, before crashing it says we have over 52 million days left on the puzzle (and 19 hours).
Not crashed the first time. All attempts to open another new window crashed
trying to share= > crash
trying to open it again 20 times= always crash
restard computer: crash on all attempts
It's like this computer is definitively not able to open it anymore.
Loading on another computer (also Windows): OK first time, crash on other attempts
Loading on a new DEVPREV same computer: OK
Exactly the same for me... It ran smoothly until I started to try sharing my solution. Now I cannot play it at all anymore. The other puzzles are working, but this won't open. :(
I did not have any errors opening this puzzle (although it did take a while to load) and it seems to be running fine. And I have an older Core i5 (first generation) ASUS running Windows 10. Go figure ...
Yesterday my fourth attempt to open the puzzle crashed in about 1/2 second. Today I got to the screen initializing before crashing. Susume reported over 52 million days left, I only get 48,798,575 days 1 hours left till the puzzle expires. What gives?
Visual Studio reports the following error:
Unhandled exception at 0x75D2DAD8 in Foldit.exe: Microsoft C++ exception: std::bad_alloc at memory location 0x0018F298.
are these molecules? ligands? what is their role?
thought it was my lucky day - then I tried creating a new track - machine crash
Was able to play puzzle until servers went down - and now cannot get it to open again - crashes foldit win 7 main
As I suggested earlier, this puzzle should be closed and re-opened as a devprev puzzle. It is unworkable for too many people.
puzzle wont' open in devprev either win 7
Just as others said it opened once without problem, then never again. Neither in main nor in deprev clients. Tried on three different computers at least 20 times: Win 7, Win 8 even on Vista. The one with Win 8 has 32 GB memory and a 3rd gen i7 CPU - the crash cannot be a resource problem.
I second gitwut suggestion: Close it and re-post as a devprev puzzle, unless it can be fixed and made playable for everyone.
-(re) install Foldit (and Devprev)
-open only once
-never share, never change track (you can save)
One client kept crashing on opening the puzzle.
After some experimentation, I tried deleting the the autosave files under
where *foldit* is the foldit install folder, 002002315 is the nodeid of puzzle 1221, *userid* is your numeric userid (it should be the only directory at this level), and autosave*.ir_solution is all the autosaved solution files.
I hadn't done anything on this client, so the autosaved files were worthless.
Deleting these files allowed the client to open the puzzle without crashing.
I suspect this files were corrupted in one of the previous crashes.
Yesterday loaded fine (albeit a bit slowly) then was fine until server blip. Today can't open it and it crashes. Loci's solution sadly didn't work for me unless I delete all the quicksaves as well, then it does open although the puzzle has been reset. Not ideal...
1221 was playing without problems 10 minutes ago. I saved current solution and tried to open an earlier saved solution. Immediate crash!
Now I cannot reload the puzzle, even with 'disable server timeouts' checked.
I agree with those who say, "Get rid of this one until problem is solved."
While it may be a memory associated issue, or maybe not, the team has passed along these helpful suggestions:
Closing other programs.
Start the puzzle on a fresh client, so that it has loaded the minimal set of data in to memory.
Upgrading any hardware, if possible. (We know that's probably not a great solution or all that practical for a lot of you so we put it last.)
In the meantime, we appreciate all the reports and your patience with this puzzle!
Followed your recommendations. I even shut down my PC and the first thing I did once up again was start foldit. Still crashed. I seriously doubt it's a memory issue.
I have a one year old i7 3.6 GHz, 12 GB ram PC running Windows 10. Unless foldit needs more than 10 GB of memory it should be fine. Other players have commented about having less powerful PCs and being able to work on the puzzle.
Just wondering (the old software QA guy in me is asking):
1. can you move the quicksaves to a temporary fold
2. start game
3. move the quicksaves back to the correct location
4. attempt to open a quicksave
Will the client crash now?
It would be interesting to see the results of this if anyone wants to try it out and report back.
@bendbob, in this case, the puzzle was crashing upon loading. I hadn't run any scripts, so I didn't have any quicksave files in the puzzles directory.
All I had was four autosaves:
I saved the files from another crashy client and took a look.
All were about 120 KB, slightly smaller than the ones from a client running on the same puzzle. The files looked reasonable on inspection. They are most binary, with a few eyecatchers such as "VRFY" near the end. I'm assuming "VRFY" is similar to the "verify" keyword found in various other foldit files.
I tried deleting the files one-by-one in the order shown. The client wouldn't start until all four were gone.
I did a shake and wiggle once the client was running and compared the new autosave files to the old ones. I don't see any obvious differences in the overall structure. It appears autosave.ir_solution gets updated from time to time, even with the client sitting idle. There is some move information (references to ActionGlobalMinimize, ActionRepack) near the end of the new file, before the PHAS, ALGN, SCOR, and VRFY eyecatchers. Bottom line, the bad files aren't obviously corrupted or truncated.
I'll be glad to share the "bad" files with the developers.
Answer is here:
All we can do is deleting the puzzle map, start again from scratch.
Forbidden:: share, close, shut down, change track, overload of the computer (e.g. using too much memory, 100% CPU etc), computer crash for other reasons (electricity disruption etc)
Allowed: save (locally), stop and start recipes, lock or screensaver, windows sleep mode, play other puzzles in other windows in parallel, hide notifications (ONLY if the network is connected !!), reset the puzzle, undos and all other tools
Risky: to play with the density map (reports of crashes when changing the threshold) but I suspect this is another (memory) problem.
In case of network disruption (no credit on the server) or hang ("freezed window", "non responding") never try anything on this client. Try to reconnect using other client, other puzzle and wait until the puzzle responds itself.
If you saved a solution, don't try to edit your comments afterwards: crash !
Finally I also crashed on saving local.
I loose my best solution rank 5 after a computer stop.
Loci's solution doesn't work for me.
When trying to open any new Foldit client, windows7 says
"The game has previously not started up corectly.If this problem persists, please install the latest version"
Completely deleted map *foldit*\puzzles\002002315
Opening: ok, a rest puzzle :(
Trying to load a saved solution: crash
this puzzle is currently not fit for purpose.
Bonus science chat is after it's closure.
I suggest the puzzle is removed and fixed - then we can have the science chat. Then the puzzle can be reposted when it's fixed. This has to be more productive than what we have now?
Unfortunately, we're just not able to move the chat due to its last minute nature - and we do plan on working on a Round 2, as noted in the news.
Thanks for the feedback as we work on making the best of a rough situation!
First, there was an omission in my previous post, the saved solutions are under:
The previous post left out *trackname*, which is "default" or the name of the track you're using.
The next part is a long sad story.
I tried stopping a client to share. Of course, the client hung due to yesterday's network outage. Anticipating this problem, I was running the procmon utility, but unfortunately it didn't give me a good idea of where the hang is. Also, I saw some Norton Security activity on the process, so I need to see what that's about. (I thought I had excluded the foldit directories from Norton's scanning, but I guess not.) I do have the procmon log if anyone's interested.
After closing the hung client, it of course crashed on restart. Deleting the autosave files in the above directory did not help. I had to delete the quicksave files as well to restart the client.
After restarting, I tried copying the quicksave files back in. There were quite a few, as the client had been running TvdL Enchanted DRW 2.8.1. Foldit apparently only checks these files at startup, so things like "save.Quickload(50)" didn't change the pose of the protein.
After closing the client again, it of course crashed again on startup. So it appears that the work done on this client has been lost, unless I can figure something out.
Why leave a puzzle up that is so obviously broken - even if it is now for zero points?
While we understand that the puzzle is not very functional for a number of players, we feel the unique scientific interest of this puzzle still makes it worth exploring for those who can, without penalizing those who can't participate with it at this time. As noted in the news post, we're hoping for a simplified Round 2 that will widen the circle of participants.
Additionally, it helps us collect data and hopefully pin down the real issues behind all the trouble. Just taking it down also limits that source of data.
Appreciate the perspective, though, we know it's a tough situation for the community to be in.
74 people have been able to log in and do some work on it. Out of that maybe 15 or 25 have been able to take it pretty far. The rest are probably locked out after crashing trying to make a new track, share etc. In fact since the scores don't seem to have moved, it is possible that everyone is now locked out. So why keep it active?
http://fold.it/portal/node/2002315#comment-32266 I think I hit a number of the points you're concerned about in this post.
I'm ok with the team decision to let this puzzle running for 0 points.
My investment would not be completely lost and no player would be penalized.
Moreover, I find it quite challenging to try a puzzle in one unique run at a time (no share, no parallel track, no stop). A kind of pure "hand fold" or "devprev-type" round without points.
A good way to train for this new type of puzzle.
Appreciate your positive attitude here! :)
I would even make it a suggestion for the "hand fold" category (or a new "soloist only" category).
Hand fold is boring and time consuming because we cannot use any lua recipe.
A "no share" puzzle type round has some identical advantages like allowing for more diverse explorations to be evolved in a second round only.
This is the 2nd time it happens. I cannot change the Threshold in ED without crashing the puzzle.
I am running latest devprev under win10.
=====>>>> This the end of the log.txt:
Playing sound: 4
***** ENDING THREAD ActionRepack
***** STARTING THREAD ActionGlobalMinimize
1: RaiseException +72 bytes (no line)
2: library_main +46809519 bytes (no line)
3: library_main +46800642 bytes (no line)
4: library_main +5260018 bytes (no line)
5: library_main +5259363 bytes (no line)
6: library_main +4929227 bytes (no line)
7: library_main +4342635 bytes (no line)
8: library_main +5222208 bytes (no line)
9: library_main +6508664 bytes (no line)
10: library_main +4688525 bytes (no line)
11: library_main +6292050 bytes (no line)
12: library_main +4003108 bytes (no line)
13: library_main +29675 bytes (no line)
14: library_main +21 bytes (no line)
15: no symbol (no line)
16: no symbol (no line)
17: no symbol (no line)
18: BaseThreadInitThunk +36 bytes (no line)
19: RtlUnicodeStringToInteger +595 bytes (no line)
20: RtlUnicodeStringToInteger +542 bytes (no line)
IRC::run error, code = 5, desc = Remote connection closed
=====>>> and debug.txt:
"build_id" : "20160331-69bf47620a-win_x86-devprev"
"crash_id" : "0d9484aa-ec53-4618-926b-c5798dd8cb21"
"current_actions" : ""
"current_tool" : ""
"file" : "core/chemical/gasteiger/GasteigerAtomTypeSet.cc:58"
"machine_id" : "09edfe6b-95dc-4576-888d-aeeae5d74622"
"macro_id" : "-1"
"message" : "Unable to open gasteiger atom type file: cmp-database-45bbcddcbd4174e67b82569775fde821\\database\\chemical/gasteiger/default/atom_type_data.txt"
"player_id" : "253386"
"puzzle_id" : "0"
"puzzle_running_time" : "2503591"
"running_time" : "2.50359e+006"
"timestamp" : "1461089008"
====>>> Note that "cmp-database-45bbcddcbd4174e67b82569775fde821\\database\\chemical/gasteiger/default/atom_type_data.txt" does not exist on my foldit install. Under 'chemical' are only: atom_type_sets, carbohydrates, element_sets, mm_atom_type_sets, orbital_type_sets and residue_type_sets.
This is how I crashed after running ok for a few hours.