Crash on Linux

Started by markm457

Hiro Protagonist Lv 1

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

Hiro Protagonist Lv 1

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

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

vakobo Lv 1

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

Bobek07 Lv 1

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

Bruno Kestemont Lv 1

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.

Bruno Kestemont Lv 1

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

Bruno Kestemont Lv 1

Linux poor performance ?

Ubuntu 17 on a Mac i7 2 cores: I can only run 2 clients (64bits) contra 3 in Mac OS (32 bits), and I have the same problems as above (Linux on a PC)

Is that because of the change 32 to 64 bits ?