Bug #28766 | MySQL crashes when tables with many partitions opened | ||
---|---|---|---|
Submitted: | 30 May 2007 8:25 | Modified: | 5 Jun 2007 15:05 |
Reporter: | Victoria Reznichenko | Email Updates: | |
Status: | Can't repeat | Impact on me: | |
Category: | MySQL Server | Severity: | S1 (Critical) |
Version: | 5.1.20 | OS: | Any |
Assigned to: | CPU Architecture: | Any |
[30 May 2007 8:25]
Victoria Reznichenko
[30 May 2007 8:26]
MySQL Verification Team
From the server error log: 070530 12:11:40 - mysqld got signal 6; 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=8388572 read_buffer_size=131072 max_used_connections=3 max_threads=151 threads_connected=2 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 337602 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. thd: 0x8fd8608 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=0xb2fd9d78, backtrace may not be correct. Stack range sanity check OK, backtrace follows: 0x8275169 0xffffe410 0xb7e15ea3 0xb7e49f8b 0xb7e4f911 0xb7e50f84 0x8656216 0x85680dd 0x853d14a 0x83c5117 0x8384ee3 0x82d4f15 0x82c9dee 0x82cc388 0x82ccfa6 0x82cd363 0x83f9263 0x83e8615 0x82ff86b 0x82fcb4f 0x83012f1 0x8283c58 0x8285471 0x828df0a 0x828ea3b 0x828fbe1 0x827d964 0xb7f8834b 0xb7ea965e New value of fp=(nil) failed sanity check, terminating stack trace! Please read http://dev.mysql.com/doc/mysql/en/using-stack-trace.html and follow instructions on how to resolve the stack trace. Resolved stack trace is much more helpful in diagnosing the problem, so please do resolve it Trying to get some variables. Some pointers may be invalid and cause the dump to abort... thd->query at 0x8fd9c78 = SHOW TABLE STATUS thd->thread_id=2 The manual page at http://www.mysql.com/doc/en/Crashing.html contains information that should help you find out what is causing the crash.
[30 May 2007 8:32]
Sveta Smirnova
test case
Attachment: bug28766.test (application/octet-stream, text), 604 bytes.
[5 Jun 2007 15:05]
MySQL Verification Team
Wasn't able to reproduce it.