# Assertion failure **URL:** \ **Category:** Other MySQL® Questions\ **Created:** [February 23, 2007, 2:31pm UTC](https://forums.percona.com/t/assertion-failure/212 "2007-02-23T14:31:23Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![fdezmichael](https://avatars.discourse-cdn.com/v4/letter/f/ee7513/32.png) [@fdezmichael](https://forums.percona.com/u/fdezmichael)\ **Post date:** [February 23, 2007, 2:31pm UTC](https://forums.percona.com/t/assertion-failure/212/1 "2007-02-23T14:31:23Z")
Hi. i am new in this forum…, i do not why in sometimes mysql crash with this error, somebody have any idea? There is a variable that i have to modify? The machine has: 2 CPU Pentium III 700 Mhz Aprox. 4 GB RAM. Redhat 7.2 Mysql version: 4.0.14-standard-log Kernel: Kernel 2.4.18-17.7 (highmem) i`ve searching in google, and i found this king of logs so many times, but i did not found a possible cause to this. * * * 070222 23:46:36 InnoDB: Assertion failure in thread 94232 in file mem0pool.c line 493 InnoDB: Failing assertion: 0 InnoDB: We intentionally generate a memory trap. InnoDB: Send a detailed bug report to [mysql@lists.mysql.com](mailto:mysql@lists.mysql.com) mysqld got signal 11; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built,or misconfigured. This error can also be caused by malfunctioning hardware. We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. key\_buffer\_size=402653184 read\_buffer\_size=2093056 max\_used\_connections=550 max\_connections=800 threads\_connected=132 It is possible that mysqld could use up to key\_buffer\_size + (read\_buffer\_size + sort\_buffer\_size)\*max\_connections = 3666809 K bytes of memory Hope that’s ok; if not, decrease some variables in the equation. thd=0x88f6e40 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong… Cannot determine thread, fp=0xbfcbe708, backtrace may not be correct. Stack range sanity check OK, backtrace follows: 0x807474f 0x82a0ad8 0x824321c 0x8241c21 0x814af0d 0x814fd3e 0x80d33e7 0x80d6bab … ---
**Author:** ![carpii](https://avatars.discourse-cdn.com/v4/letter/c/b5ac83/32.png) [@carpii](https://forums.percona.com/u/carpii)\ **Post date:** [February 23, 2007, 5:49pm UTC](https://forums.percona.com/t/assertion-failure/212/2 "2007-02-23T17:49:56Z")
Did you compile mysql yourself, or using the prebuilt binaries provided by mysql? If you compiled it, make sure all your libraries are up to date and rebuild If youre using the binary, follow the instructions and submit a bug report ---
**Author:** ![Peter](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/peter/32/2_2.png) [@Peter](https://forums.percona.com/u/Peter)\ **Post date:** [February 23, 2007, 6:24pm UTC](https://forums.percona.com/t/assertion-failure/212/3 "2007-02-23T18:24:47Z")
Before looking at anything else I’d suggest to update MySQL to recent version. 4.0.14 is probably over 2 years old and no one will look into bugs with it right now.