Crash on Linux

Case number:845829-995351
Topic:Crash/Hang
Opened by:markm457
Status:Open
Type:Bug
Opened on:Tuesday, June 18, 2013 - 11:13
Last modified:Monday, October 30, 2017 - 14:24

Foldit crashed after ~3 hours of execution. This was the first run of a new Foldit install on a Debian Linux 64-bit OS machine. The last portion of the log file is attached.

AttachmentSize
log_crash_130617_tail.txt15.17 KB
(Tue, 06/18/2013 - 11:13  |  17 comments)


drjr's picture
User offline. Last seen 14 hours 48 min ago. Offline
Joined: 06/27/2009

foldit crashes on ubuntu 13.04 between 5 min to 1 hour (64-bit)

katfish's picture
User offline. Last seen 3 years 5 weeks ago. Offline
Joined: 01/09/2013

Thanks for bringing this to our attention markm. We'll do some investigating into this.

Joined: 09/20/2011
Groups: None

Crash after autodownload:
$ ./Foldit
Foldit Error: The game has previously not started up correctly.
If this problem persists, please install the latest version.
terminate called after throwing an instance of 'std::logic_error'
what(): basic_string::_S_construct null not valid
Aborted

----
The actual version of Foldit (2013-06-12-e0a72c602f-linux_x64)
repeatedly crashes on exit.

Joined: 09/20/2011
Groups: None

crashdump during normal run of program see attachment

Joined: 09/20/2011
Groups: None

Foldit is still crashing after change to other puzzle and close
and sometimes only after changing to annother puzzle (according log as attachment)

Joined: 09/21/2011
Groups: Void Crushers

Cherry, this looks like a corrupt filesystem if I am correct. Use fsck to check and if needed repair.
Of course I can be wrong. Just something to check.

GuidoJ's picture
User offline. Last seen 7 weeks 5 days ago. Offline
Joined: 09/19/2011

I'm experiencing similar problems and as a matter of fact fsck ran a couple of days ago and that didn't fix the problem.

I also get this:
*** glibc detected *** ./Foldit: corrupted double-linked list: 0x0000000000c872c0 ***
Segmentation fault

and this:
terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc
Aborted

regularly while running the linux client.

Whenever there's a new binary and the client is restarted I also get the same messages cherry39 mentioned earlier (I've been experiencing this for months I think). BTW the message indicates exactly what is wrong: an std::string is constructed with a null pointer (essentially something along the line of "std::string myString(0);", although in the actual code it's probably less obvious ...)

GuidoJ's picture
User offline. Last seen 7 weeks 5 days ago. Offline
Joined: 09/19/2011

FYI: Right after updating to the latest version today on linux, I get this error:

terminate called after throwing an instance of 'std::logic_error'
what(): basic_string::_S_construct null not valid
Aborted

GuidoJ's picture
User offline. Last seen 7 weeks 5 days ago. Offline
Joined: 09/19/2011

On restart I get this (which was to be expected):

Foldit Error: The game has previously not started up correctly.
If this problem persists, please install the latest version.

GuidoJ's picture
User offline. Last seen 7 weeks 5 days ago. Offline
Joined: 09/19/2011

After playing around a bit with a beginner puzzle the client crashed when running the Blue Fuze script with this error:

terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc
Aborted

GuidoJ's picture
User offline. Last seen 7 weeks 5 days ago. Offline
Joined: 09/19/2011

Normal exit (I didn't even open a puzzle) still gives this error:

*** glibc detected *** ./Foldit: corrupted double-linked list: 0x0000000000cfc010 ***

vakobo's picture
User offline. Last seen 1 year 27 weeks ago. Offline
Joined: 06/05/2008
Groups: Russian team

Linux mint 15 KDE 64 bit - crash during script execution after few minutes if Foldit window isn't top window.

Lecc's picture
User offline. Last seen 3 years 25 weeks ago. Offline
Joined: 02/14/2012
Groups: Russian team

Linux Mint 13 Mate (linux-3.2.0). The same problem as above.

Bobek07's picture
User offline. Last seen 1 year 42 weeks ago. Offline
Joined: 01/15/2016
Groups: None

Intro Puzzle 5-3 Electron Density crashes each time I try to use Wiggle All or Shake:
"terminate called after throwing an instance of 'std::bad_alloc'
terminate called recursively
what(): std::bad_alloc"

However the first time (new installation) I got a different error:
"*** Error in `./Foldit': double free or corruption (fasttop): 0x00007fc8ec26f750 ***"

My system: Linux Mint 17.2 Cinnamon 64 bit

Foldit:
version-binary: b789a7e3429244a3ddeb5742d0fc437e
version-resources: 30f143a66688c2217ee896e577fea1df
version-database: cac5f89f6a3e41d011cb430d73d6fb1b

Joined: 07/24/2017
Groups: None

Same problem for me. Running on Ubuntu 16.04

Joined: 09/24/2012
Groups: Go Science

Ubuntu 16.04: crash on deleting a track.

When I delete a track, Foldit client simply closes 50% of the time. When it happens, every client closes at any occasion without notice. The only way to solve this is to shut down and start again.

Joined: 09/24/2012
Groups: Go Science

Linux Ubuntu 16 OS. 4 cores (8 virtual processors as seen from Windows)

When at least 1 heavy puzzle is present (high memory usage), random clients crash (so I can start with 5 clients and come back after a night with only 3 clients left). The crashing client seems to be random.

It might stabilize to 2-3 clients (even with a total memory and CPU usages <50%) or end with 0 clients left.

With only small puzzles, I can open up to 7 clients if CPU and memory remain respectively about <70% and <95%. If a heavy puzzle is present in a client, random clients (same or others) might crash.

My interpretation is that this problem occurs when more than 1 processor is needed for 1 puzzle. Then it's like the client tries to get help from other processors, making the related client to crash ("randomly").

Most of the time (not always), the work is lost for the crashed client. Many times, the related track cannot be open again (immediate crash when trying to open this track), even after rebooting the computer.

I suspect it's linked to this:
"Focus on what's causing Memory Allocation Errors for Mac and Linux":
https://fold.it/portal/node/2003705

and possibly to this:
Client performance - CPU/GPU usage - summary
https://fold.it/portal/node/990207

and to this for specific puzzles:
1434 lost my work after a crash
https://fold.it/portal/node/2004260

Sitemap

Developed by: UW Center for Game Science, UW Institute for Protein Design, Northeastern University, Vanderbilt University Meiler Lab, UC Davis
Supported by: DARPA, NSF, NIH, HHMI, Microsoft, Adobe, RosettaCommons