[Linux] Fatal Error: double free or corruption

[Mother[MGA]]

There is no Ooops message; the game will randomly crash to desktop. Sometimes I can play for hours, other times it will occur in minutes. It has only happened to me in multiplayer, but I play single player very little.


# Full Error when run from the command line:
[7 Days To Die] LD_LIBRARY_PATH=~/.steam/bin32/ ~/.steam/bin32/steam-runtime/run.sh ./7DaysToDie.sh
*** Error in `./7DaysToDie.x86_64': double free or corruption (!prev): 0x000000003dc75de0 ***
Aborted (core dumped)

# Error log is here:
http://pastebin.com/ACEM7TzT

# OS: Ubuntu 14.04.1 LTS
# uname -a
Linux pc 3.13.0-36-generic #63-Ubuntu SMP Wed Sep 3 21:30:07 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

# cat /proc/cpuinfo
http://pastebin.com/BKQus3AD

# cat /proc/meminfo
http://pastebin.com/hcDFWQAf

# lshw
http://pastebin.com/he6jx3zt

[LunaCPlays]

PulseAudio is probably what's generating it. Can't say for sure but upon first look I would try running it with that disabled. I'll keep going through the logs as well.

[Mother[MGA]]

I ran the game without pulseaudio using :
pasuspender ~/.steam/bin32/steam-runtime/run.sh ./7DaysToDie.sh

The game loaded and produced no sound. I exited and did not try to reproduce the problem.

How can I run the game without pulseaudio and still have sound?

[Eldaranth]

I'm seeing this same issue (except single player). Did you figure out a workaround?

[Mother[MGA]]

Sorry Eldaranth. I haven't had this problem since A15.

[CptnHarlock]

The "double free or corruption (!prev) error" is a typical programming error that has to do with accessing or trying to free memory in a bungled way. So there is nothing you as a user can do except reporting the error. It's normaly at the end of an array so if the array is large enough you will seldom hit that "bad" part. But once you do your program crashes. So - go to the official forums and post the log.

Menwhile some freewheeling speculation to be taken with a truck of salt:
If it's a failed acces of memory because of a bad array what you can do to try to avoid the bug is to keep an eye on what you were doing when it happened. For example if you were using an unusual block; If you were putting on a rare hat or a some other clothing item which may be at the end of an array list. Avoid doing that again since that is probably what triggers the error. If it's a bungled memmory freeing action - then you're f*cked. :)