"*** glibc detected *** double free or corruption:" messages appear in the console or in /var/log/messages.

Created:

2016-11-16 12:48:56 UTC

Modified:

2017-05-23 07:25:14 UTC

6

Was this article helpful?


Have more questions?

Submit a request

"*** glibc detected *** double free or corruption:" messages appear in the console or in /var/log/messages.

Applicable to:

  • Plesk Sitebuilder 4.5 for Linux

Symptoms

Time to time I see:

    \\*\\*\\* glibc detected \\*\\*\\* double free or corruption: 0x0937d008 \\*\\*\\*

messages on my Fedora Core server in the console or in it /var/log/message log.

Cause

The version of glibc provided with Fedora Core performs additional internal sanity checks to prevent and detect data corruption as early as possible. By default, should corruption be detected, a message similar to the following will be displayed on standard error (or logged via syslog if stderr is not open):

\\*\\*\\* glibc detected \\*\\*\\* double free or corruption: 0x0937d008 \\*\\*\\*

By default, the program that generated this error will also be killed. However, this (and whether or not an error message is generated) can be controlled via the MALLOC\ CHECK\ environment variable. The following settings are supported:

0 — Do not generate an error message, and do not kill the program
1 — Generate an error message, but do not kill the program
2 — Do not generate an error message, but kill the program
3 — Generate an error message and kill the program

Note, if MALLOC\ CHECK\ is explicitly set a value other than 0, this causes glibc to perform more tests that are more extensive than the default, and may impact performance.

Resolution

If some application fails due to similar error, you can set MALLOC\ CHECK\ to zero with:

    # export MALLOC_CHECK_=0

and try to run the application again.

If you wish to set this variable permanently you can put it into /etc/profile .

Have more questions? Submit a request
Please sign in to leave a comment.