MariaDB crashes in write_tail on a select from UTF8 tables with a simple join and order by
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MariaDB |
Fix Released
|
High
|
Michael Widenius |
Bug Description
Hi guys
We've found a query that crashes MariaDB both 5.2.9 and 5.2.10. This query is generated by CMS Joomla with Virtuemart plugin.
Used platform: Debian GNU/Linux Squeeze amd64.
The query:
SELECT SQL_CALC_FOUND_ROWS * FROM `i1rsk_
I can also provide a test sql dump of database to reproduce this problem, but I can't be published, so I'd prefer to send it to someone's e-mail directly if possible.
After executing this query, MariaDB crashes with the following information written in log:
111229 9:28:14 [ERROR] 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=0
read_buffer_
max_used_
max_threads=402
threads_connected=1
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x7f15067c6ef0
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...
stack_bottom = 0x7f14e7b57e98 thread_stack 0x48000
/usr/sbin/
/usr/sbin/
/lib/libpthread
/lib/libc.
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/lib/libpthread
/lib/libc.
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0x7f15067e9278): SELECT SQL_CALC_FOUND_ROWS * FROM `i1rsk_
Connection ID (thread ID): 12
Status: NOT_KILLED
Related branches
Changed in maria: | |
assignee: | nobody → Oleksandr "Sanja" Byelkin (sanja-byelkin) |
Changed in maria: | |
importance: | Undecided → High |
Changed in maria: | |
status: | New → In Progress |
Changed in maria: | |
status: | Confirmed → In Progress |
Changed in maria: | |
status: | Fix Committed → Fix Released |
Umm, just noticed: the log dump says that key_buffer_size=0, which is wrong. Actual value:
MariaDB [(none)]> show variables like "key_buffer_size"; ------- ----+-- ------- --+ ------- ----+-- ------- --+ ------- ----+-- ------- --+
+------
| Variable_name | Value |
+------
| key_buffer_size | 134217728 |
+------
1 row in set (0.00 sec)