Lots of people are crashing on 1266; let's have a thread! Why not keep it all in the puzzle comments? Because you can't upload a log.txt file in the puzzle comments.
This crash: clicked "Center Protein on Density." Nothing happened for a while, then it crashed. log.txt attached - as usual, I cut several MB of nulls out of the file before uploading. There is an error message before the unhandled exception, but the unhandled exception itself is… dun dun dun… an OpenAL function call. (There was another client open; I assume that one wrote the lines after the exception.)
Yep same hear. I bet your machine is on win 10 susume!
I agree this 1266 is unplayable.
Even crashed just doing a wiggle@1.0 of 65-69 on Auto.
Nope, Win 7. I never had the crashing-every-five-minutes problem that the Win 10 users have had - just an odd openAL error here or there.
20160728-c4d88693d5-win_x86-devprev
Thanks for letting us know! There have been a lot of problems with Puzzle 1266, so we've made it a non-competitive puzzle (worth zero points), but still available to anyone who wants to tinker with it.
I have an idea about the issue with Center Protein on Density. The log file will help to confirm, but it's definitely unrelated to the OpenAL exceptions.
@bertro, your wiggle crash appears to be related to an ongoing symmetry bug that has been really difficult to crack. It's helpful to know that this bug is also rearing its head with crystal symmetry.
@bkoep: Are you able to duplicate the crash?
1266 wont stay launched; reading the crash logs makes me think it has something to do with chat.
MAC OS 10.11.6
Attaching Fold log and MAC Crash Log
Kind of… We've been able to generate similar crashes, but not reliably or reproducibly. It appears that Foldit can sometimes "break symmetry," but the event seems to be non-deterministic—or at least very finicky. We can repeat the same steps many times, but only rarely does the problem occur.
If you have a case in which this asymmetry error occurs reliably (e.g. "load this solution, wiggle all, crash on tenth iteration"), that would be a huge help to us.
you mean this error I guess: "asymmetry introduced by ActionRepack"?
I'll sure share if it happens.
Sorry I cannot replicate.
However, this may help or not:
It was crashing everytime (as stated before here) while I had, in the same foldit directory, a previous version of devprev running puzzle 1264 at the same time. Meaning, 1264 was running a script. From that same directory, I started a new client but it updated to the latest devprev and I opened 1266 which stared crashing doing only a wiggle on the selected segments on auto.
I don't know if it is relevant. I cannot test this since I lost the previous devprev…
