Thank you for the bug report. This is easy to confirm with previous version, 5.6.21-71.0 as well:
[openxs@chief p5.6]$ bin/mysql -uroot test
Reading table information for completion of table and column names
You can turn off this feature to get a quicker startup with -A
Welcome to the MySQL monitor. Commands end with ; or \g.
Your MySQL connection id is 1
Server version: 5.6.21-70.0 MySQL Community Server (GPL)
Copyright (c) 2009-2014 Percona LLC and/or its affiliates
Copyright (c) 2000, 2014, Oracle and/or its affiliates. All rights reserved.
Oracle is a registered trademark of Oracle Corporation and/or its
affiliates. Other names may be trademarks of their respective
owners.
Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.
mysql> drop table if exists `t1`;
Query OK, 0 rows affected, 1 warning (0.00 sec)
mysql> insert into `t1` values (6,repeat('a',1000),repeat('a',423),repeat('a',827), repeat('a',759));
ERROR 2013 (HY000): Lost connection to MySQL server during query
mysql> 150114 09:02:06 mysqld_safe Number of processes running now: 0
150114 09:02:06 mysqld_safe mysqld restarted
mysql> exit
Bye
[openxs@chief p5.6]$ tail -100 data/chief.err
2015-01-14 09:01:38 2152 [Note] /home/openxs/dbs/p5.6/bin/mysqld: ready for connections.
Version: '5.6.21-70.0' socket: '/tmp/mysql.sock' port: 3306 MySQL Community Server (GPL)
InnoDB: unknown error code 1000
2015-01-14 09:02:06 7fe6350aa700 InnoDB: Assertion failure in thread 140626709096192 in file row0mysql.cc line 688
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
07:02:06 UTC - 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.
Please help us make Percona Server better by reporting any
bugs at http://bugs.percona.com/
key_buffer_size=8388608
read_buffer_size=131072
max_used_connections=1
max_threads=153
thread_count=1
connection_count=1
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 69184 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x7fe624b94000
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 = 7fe6350a9df0 thread_stack 0x40000
/home/openxs/dbs/p5.6/bin/mysqld(my_print_stacktrace+0x35)[0x908875]
/home/openxs/dbs/p5.6/bin/mysqld(handle_fatal_signal+0x4b4)[0x66f4d4]
/lib64/libpthread.so.0[0x3ffac0eeb0]
/lib64/libc.so.6(gsignal+0x35)[0x3ffa8330c5]
/lib64/libc.so.6(abort+0x186)[0x3ffa834a76]
/home/openxs/dbs/p5.6/bin/mysqld[0xa530d2]
/home/openxs/dbs/p5.6/bin/mysqld[0xa5464b]
/home/openxs/dbs/p5.6/bin/mysqld[0x9bc7d0]
/home/openxs/dbs/p5.6/bin/mysqld(_ZN7handler12ha_write_rowEPh+0xab)[0x5b296b]
/home/openxs/dbs/p5.6/bin/mysqld(_Z12write_recordP3THDP5TABLEP9COPY_INFOS4_+0x7c)[0x6d459c]
/home/openxs/dbs/p5.6/bin/mysqld(_Z12mysql_insertP3THDP10TABLE_LISTR4ListI4ItemERS3_IS5_ES6_S6_15enum_duplicatesb+0x10ef)[0x6d7e6f]
/home/openxs/dbs/p5.6/bin/mysqld(_Z21mysql_execute_commandP3THD+0x264d)[0x6f0dad]
/home/openxs/dbs/p5.6/bin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x618)[0x6f6e38]
/home/openxs/dbs/p5.6/bin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x15c5)[0x6f8495]
/home/openxs/dbs/p5.6/bin/mysqld(_Z24do_handle_one_connectionP3THD+0x15f)[0x6c1bff]
/home/openxs/dbs/p5.6/bin/mysqld(handle_one_connection+0x47)[0x6c1cd7]
/home/openxs/dbs/p5.6/bin/mysqld(pfs_spawn_thread+0x12a)[0x99620a]
/lib64/libpthread.so.0[0x3ffac06ccb]
/lib64/libc.so.6(clone+0x6d)[0x3ffa8e0c2d]
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (7fe616c1d010): insert into `t1` values (6,repeat('a',1000),repeat('a',423),repeat('a',827), repeat('a',759))
Connection ID (thread ID): 1
Status: NOT_KILLED
You may download the Percona Server operations manual by visiting http://www.percona.com/software/percona-server/. You may find information
in the manual which will help you identify the cause of the crash.
150114 09:02:06 mysqld_safe Number of processes running now: 0
150114 09:02:06 mysqld_safe mysqld restarted
...
Thank you for the bug report. This is easy to confirm with previous version, 5.6.21-71.0 as well:
[openxs@chief p5.6]$ bin/mysql -uroot test
Reading table information for completion of table and column names
You can turn off this feature to get a quicker startup with -A
Welcome to the MySQL monitor. Commands end with ; or \g.
Your MySQL connection id is 1
Server version: 5.6.21-70.0 MySQL Community Server (GPL)
Copyright (c) 2009-2014 Percona LLC and/or its affiliates
Copyright (c) 2000, 2014, Oracle and/or its affiliates. All rights reserved.
Oracle is a registered trademark of Oracle Corporation and/or its
affiliates. Other names may be trademarks of their respective
owners.
Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.
mysql> drop table if exists `t1`;
Query OK, 0 rows affected, 1 warning (0.00 sec)
mysql> create table `t1`(`a` int,`c` blob,`d` blob,`e` blob,`f` blob,primary key (`a`)) engine=innodb;
Query OK, 0 rows affected (0.65 sec)
mysql> insert into `t1` values (1,'a', repeat( 'a',786) ,repeat( 'a',826) , repeat('a',42));
Query OK, 1 row affected (0.06 sec)
mysql> insert into `t1` values (2,'a', repeat( 'a',488) ,repeat( 'a',1005) ,repeat( 'a',489) );
Query OK, 1 row affected (0.04 sec)
mysql> insert into `t1` values (3,repeat('a',953), repeat( 'a',990) ,repeat( 'a',614) , repeat('a',1000));
Query OK, 1 row affected (0.08 sec)
mysql> insert into `t1` values (4,repeat('a',661), repeat( 'a',236) ,repeat( 'a',911) , repeat('a',67));
Query OK, 1 row affected (0.09 sec)
mysql> insert into `t1` values (5,repeat( 'a',1000) ,repeat( 'a',423) ,repeat( 'a',827) , repeat('a',759));
Query OK, 1 row affected (0.04 sec)
mysql> set session innodb_fake_changes = 1 ;
Query OK, 0 rows affected (0.00 sec)
mysql> insert into `t1` values (6,repeat( 'a',1000) ,repeat( 'a',423) ,repeat( 'a',827) , repeat('a',759));
ERROR 2013 (HY000): Lost connection to MySQL server during query
mysql> 150114 09:02:06 mysqld_safe Number of processes running now: 0
150114 09:02:06 mysqld_safe mysqld restarted
mysql> exit dbs/p5. 6/bin/mysqld: ready for connections. bugs.mysql. com. dev.mysql. com/doc/ refman/ 5.6/en/ forcing- innodb- recovery. html bugs.percona. com/
Bye
[openxs@chief p5.6]$ tail -100 data/chief.err
2015-01-14 09:01:38 2152 [Note] /home/openxs/
Version: '5.6.21-70.0' socket: '/tmp/mysql.sock' port: 3306 MySQL Community Server (GPL)
InnoDB: unknown error code 1000
2015-01-14 09:02:06 7fe6350aa700 InnoDB: Assertion failure in thread 140626709096192 in file row0mysql.cc line 688
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://
InnoDB: about forcing recovery.
07:02:06 UTC - 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.
Please help us make Percona Server better by reporting any
bugs at http://
key_buffer_ size=8388608 size=131072 connections= 1 size)*max_ threads = 69184 K bytes of memory
read_buffer_
max_used_
max_threads=153
thread_count=1
connection_count=1
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x7fe624b94000 dbs/p5. 6/bin/mysqld( my_print_ stacktrace+ 0x35)[0x908875] dbs/p5. 6/bin/mysqld( handle_ fatal_signal+ 0x4b4)[ 0x66f4d4] libpthread. so.0[0x3ffac0ee b0] libc.so. 6(gsignal+ 0x35)[0x3ffa833 0c5] libc.so. 6(abort+ 0x186)[ 0x3ffa834a76] dbs/p5. 6/bin/mysqld[ 0xa530d2] dbs/p5. 6/bin/mysqld[ 0xa5464b] dbs/p5. 6/bin/mysqld[ 0x9bc7d0] dbs/p5. 6/bin/mysqld( _ZN7handler12ha _write_ rowEPh+ 0xab)[0x5b296b] dbs/p5. 6/bin/mysqld( _Z12write_ recordP3THDP5TA BLEP9COPY_ INFOS4_ +0x7c)[ 0x6d459c] dbs/p5. 6/bin/mysqld( _Z12mysql_ insertP3THDP10T ABLE_LISTR4List I4ItemERS3_ IS5_ES6_ S6_15enum_ duplicatesb+ 0x10ef) [0x6d7e6f] dbs/p5. 6/bin/mysqld( _Z21mysql_ execute_ commandP3THD+ 0x264d) [0x6f0dad] dbs/p5. 6/bin/mysqld( _Z11mysql_ parseP3THDPcjP1 2Parser_ state+0x618) [0x6f6e38] dbs/p5. 6/bin/mysqld( _Z16dispatch_ command19enum_ server_ commandP3THDPcj +0x15c5) [0x6f8495] dbs/p5. 6/bin/mysqld( _Z24do_ handle_ one_connectionP 3THD+0x15f) [0x6c1bff] dbs/p5. 6/bin/mysqld( handle_ one_connection+ 0x47)[0x6c1cd7] dbs/p5. 6/bin/mysqld( pfs_spawn_ thread+ 0x12a)[ 0x99620a] libpthread. so.0[0x3ffac06c cb] libc.so. 6(clone+ 0x6d)[0x3ffa8e0 c2d]
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 = 7fe6350a9df0 thread_stack 0x40000
/home/openxs/
/home/openxs/
/lib64/
/lib64/
/lib64/
/home/openxs/
/home/openxs/
/home/openxs/
/home/openxs/
/home/openxs/
/home/openxs/
/home/openxs/
/home/openxs/
/home/openxs/
/home/openxs/
/home/openxs/
/home/openxs/
/lib64/
/lib64/
Trying to get some variables. 'a',1000) ,repeat( 'a',423) ,repeat( 'a',827) , repeat('a',759))
Some pointers may be invalid and cause the dump to abort.
Query (7fe616c1d010): insert into `t1` values (6,repeat(
Connection ID (thread ID): 1
Status: NOT_KILLED
You may download the Percona Server operations manual by visiting www.percona. com/software/ percona- server/. You may find information
http://
in the manual which will help you identify the cause of the crash.
150114 09:02:06 mysqld_safe Number of processes running now: 0
150114 09:02:06 mysqld_safe mysqld restarted
...