[NewChapter] multiple client crashes on refinement puzzle
Case number: | 845829-996704 |
Topic: | Crash/Hang |
Opened by: | gitwut |
Status: | Open |
Type: | Bug |
Opened on: | Tuesday, January 21, 2014 - 03:52 |
Last modified: | Tuesday, February 4, 2014 - 23:05 |
20140117-46727380f0-win_x86-newchapter
The client crashed 5 times over a 4-5 hour period.
Once when I clicked the stop script button while Idealize script was running.
Once when I clicked wiggle after changing wiggle power from medium to high.
The other three times occurred while scripts were running.
I'll attach log files of future crashes.
We're posting an update shortly that should address crashes during wiggle.
The De-novo crashed on me today in a very similar manner. It was rebuilding for awhile on Medium wiggle power. I changed it to high power and the client died when I clicked Wiggle. There are two other clients running on the same computer, so I'm not sure that a copy of the log would help or not.
De-novo crashed again this morning. I'm attaching a screen shot (shows script running and step/iteration). Windows crash message below:
Problem signature:
Problem Event Name: APPCRASH
Application Name: Foldit.exe
Application Version: 0.0.0.0
Application Timestamp: 4f5e8578
Fault Module Name: KERNELBASE.dll
Fault Module Version: 6.1.7601.18229
Fault Module Timestamp: 51fb1116
Exception Code: e06d7363
Exception Offset: 0000c41f
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789
Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409
If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt
De-novo crashed again, during a script run:
Problem signature:
Problem Event Name: APPCRASH
Application Name: Foldit.exe
Application Version: 0.0.0.0
Application Timestamp: 4f5e8578
Fault Module Name: KERNELBASE.dll
Fault Module Version: 6.1.7601.18229
Fault Module Timestamp: 51fb1116
Exception Code: e06d7363
Exception Offset: 0000c41f
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789
Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409
If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt
Thanks for all the feedback. Reproduced this issue and forwarded to the developers.
So far I've only been able to reproduce this on the de-novo as well. Have you or any others encountered this on the other two posted puzzles?
I don't recall encountering it on either of the other puzzles using the current client version.
I've encountered the hang while running scripts on both 839 and 837, in addition to 838 multiple times after the above posts.
I'm tired of having to restart clients all the time. As much as I hate doing it, I'm considering dropping down to one client per puzzle--playing the higher score of either my solo or the team's evo. That's not good for diversity, but the problem is too frustrating and wastes too much time.
I had the same experience last night (1/30/14 PST). I had gained 85 points on medium wiggle. I stopped the wiggle and changed to high power to see what more I could get. I hit W and Foldit immediately crashed. (Also my 85 points from the medium wiggle disappeared. I had to regain them all over again.) [Win7 64bit. 2.2Ghz processor, 6GB RAM.]
PS. Was working on 838 Denovo.
As per the comment here: http://fold.it/portal/node/996820
We are working on resolving this issue currently.
It ran smoothly over night and most of today. I applied MS updates, rebooted and started Quickfix 1.5 (using default medium wiggle power). I stopped the script after several minutes, opened the behavior menu and clicked high wiggle power. I don't recall if it crashed immediately or after I pressed the wiggle button, but it was one or the other. The log file is attached.