Article ID: 4611, created on Mar 28, 2008, last review on May 11, 2014

  • Applies to:
  • Plesk Sitebuilder 4.5 for Linux/Unix


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.


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.


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.

Search Words

double free or corruption:

glibc detected

*** glibc detected *** double free or corruption:

56797cefb1efc9130f7c48a7d1db0f0c d055be4fdc562a8ecb8e6d0bf419f946 fad6dc0c8e983c17ae70a51ac7952cd0 f7f840260c1591440648a375a64b5b75 ea6a61e571a858aa6019ceb068ea403a

Email subscription for changes to this article
Save as PDF