rpl.rpl_colSize failed in buildbot, server crashed

rpl.rpl_colSize 'row'                    w1 [ fail ]

        Test ended at 2018-04-11 11:53:54

CURRENT_TEST: rpl.rpl_colSize

Server [mysqld.2 - pid: 31302, winpid: 31302, exit: 256] failed during test run

Server log from this test:

----------SERVER LOG START-----------

2018-04-11 11:53:54 70367486636992 [Note] 'CHANGE MASTER TO executed'. Previous state master_host='127.0.0.1', master_port='16020', master_log_file='', master_log_pos='4'. New state master_host='127.0.0.1', master_port='16020', master_log_file='master-bin.000001', master_log_pos='4'.

2018-04-11 11:53:54 70367487816640 [Note] Slave SQL thread initialized, starting replication in log 'master-bin.000001' at position 4, relay log './slave-relay-bin.000001' position: 4

2018-04-11 11:53:54 70367488209856 [Note] Slave I/O thread: connected to master 'root@127.0.0.1:16020',replication started in log 'master-bin.000001' at position 4

2018-04-11 11:53:54 70367487816640 [Note] Error reading relay log event: slave SQL thread was killed

2018-04-11 11:53:54 70367487816640 [Note] Slave SQL thread exiting, replication stopped in log 'master-bin.000001' at position 466

2018-04-11 11:53:54 70367488209856 [Note] Slave I/O thread exiting, read up to log 'master-bin.000001', position 466

2018-04-11 11:53:54 70367487816640 [Note] Slave SQL thread initialized, starting replication in log 'FIRST' at position 0, relay log './slave-relay-bin.000001' position: 4

2018-04-11 11:53:54 70367488209856 [Note] Slave I/O thread: connected to master 'root@127.0.0.1:16020',replication started in log 'FIRST' at position 4

2018-04-11 11:53:54 70367487816640 [Note] Error reading relay log event: slave SQL thread was killed

2018-04-11 11:53:54 70367487816640 [Note] Slave SQL thread exiting, replication stopped in log 'master-bin.000001' at position 1964

180411 11:53:54 [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.

To report this bug, see https://mariadb.com/kb/en/reporting-bugs

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.

Server version: 10.1.33-MariaDB-1~stretch

key_buffer_size=1048576

read_buffer_size=131072

max_used_connections=4

max_threads=153

thread_count=4

It is possible that mysqld could use up to 

key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 62939 K  bytes of memory

Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x3fffa8420008

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 = 0x3fffb51d5fe8 thread_stack 0x48400

2018-04-11 11:53:54 70367488209856 [Note] Slave I/O thread exiting, read up to log 'master-bin.000001', position 1964

/usr/sbin/mysqld(my_print_stacktrace+0x68)[0x2703e768]

/usr/sbin/mysqld(handle_fatal_signal+0x430)[0x26a46b50]

linux-vdso64.so.1(__kernel_sigtramp_rt64+0x0)[0x3fffb60e04d8]

/usr/sbin/mysqld(_ZN14rpl_group_info19unmark_start_commitEv+0x34)[0x269408e4]

[0x3fffb51d5750]

/usr/sbin/mysqld(_Z17ha_rollback_transP3THDb+0x364)[0x26a4aff4]

/usr/sbin/mysqld(_Z14trans_rollbackP3THD+0x78)[0x269613f8]

/usr/sbin/mysqld(_ZN3THD7cleanupEv+0x148)[0x26811f98]

/usr/sbin/mysqld(_ZN3THDD1Ev+0x7c8)[0x26812b48]

/usr/sbin/mysqld(_ZN3THDD0Ev+0x28)[0x26812ce8]

/usr/sbin/mysqld(handle_slave_sql+0x1d88)[0x267b62d8]

/usr/sbin/mysqld(+0x973bb4)[0x26d73bb4]

2018-04-11 11:53:54 70367486636992 [Note] 'CHANGE MASTER TO executed'. Previous state master_host='127.0.0.1', master_port='16020', master_log_file='master-bin.000001', master_log_pos='1964'. New state master_host='127.0.0.1', master_port='16020', master_log_file='', master_log_pos='1964'.

/lib/powerpc64le-linux-gnu/libpthread.so.0(+0x80dc)[0x3fffb60980dc]

/lib/powerpc64le-linux-gnu/libc.so.6(clone+0x98)[0x3fffb5811528]

Trying to get some variables.

Some pointers may be invalid and cause the dump to abort.

Query (0x0): 

Connection ID (thread ID): 160

Status: KILL_CONNECTION

Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,engine_condition_pushdown=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_with_cache=on,semijoin_with_cache=on,join_cache_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=off,table_elimination=on,extended_keys=on,exists_to_in=on,orderby_uses_equalities=off

The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains

information that should help you find out what is causing the crash.

Writing a core file

----------SERVER LOG END-------------

mysqltest failed but provided no output

The result from queries just before the failure was:

< snip >

  `d` bit(11) DEFAULT NULL,

  `e` bit(11) DEFAULT NULL

) ENGINE=MyISAM DEFAULT CHARSET=latin1

Insert some values and select them on master

SELECT BIN(a), BIN(b), BIN(c), BIN(d), BIN(e) FROM t1;

BIN(a)	BIN(b)	BIN(c)	BIN(d)	BIN(e)

1010101	10101011	101010110101010101111	10101010101	10101011111

SHOW CREATE TABLE t1;

Table	Create Table

t1	CREATE TABLE `t1` (

  `a` bit(16) DEFAULT NULL,

  `b` bit(22) DEFAULT NULL,

  `c` bit(54) DEFAULT NULL,

  `d` bit(25) DEFAULT NULL,

  `e` bit(13) DEFAULT NULL

) ENGINE=MyISAM DEFAULT CHARSET=latin1

*** Cleanup  ***

DROP TABLE t1;

SET GLOBAL SLAVE_TYPE_CONVERSIONS = @saved_slave_type_conversions;

include/rpl_end.inc