I just had this happen, with the following as first lines of the errorlog:<br><br><blockquote style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;" class="gmail_quote">100216 17:48:01 [ERROR] /usr/sbin/mysqld: Incorrect key file for table '/var/tmp/#sql_46b2_0.MYI'; try to repair it<br>
100216 17:48:02 [ERROR] /usr/sbin/mysqld: Incorrect key file for table '/var/tmp/#sql_46b2_0.MYI'; try to repair it<br>*** glibc detected *** /usr/sbin/mysqld: double free or corruption (out): 0x00002aaadd97b630 ***<br clear="all">
</blockquote><div><br>I know what I was doing, though, so I suspect the following scenario:<br><br>* I was doing stuff, which filled up the /var/tmp filesystem<br>* MySQL can't write some tmp tables, notices they're incorrect and tries to repair them<br>
* In the repair thread, it hits the glibc issue.<br><br>I have also traced the thread (and thus, query) that caused it, and like Łukasz' post above, it's a pretty complex query with joins, wich indeed leads to the probable use of tmp tables.<br>
<br>On the MySQL boards I find reference to this bug (on ndb), and it maybe being fixed with a number of memory leak fixes in 5.1.10: <a href="http://bugs.mysql.com/bug.php?id=19154">http://bugs.mysql.com/bug.php?id=19154</a><br>
<br></div>-- <br>Bier met grenadyn<br>Is als mosterd by den wyn<br>Sy die't drinkt, is eene kwezel<br>Hy die't drinkt, is ras een ezel<br>