Full-text search of the utf8mb4 column causes crash

160422 12:27:27 [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 http://kb.askmonty.org/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.0.24-MariaDB-1~trusty-wsrep

key_buffer_size=16777216

read_buffer_size=131072

max_used_connections=10

max_threads=502

thread_count=3

It is possible that mysqld could use up to

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

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

Thread pointer: 0x0x7f8bb9ddb008

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 = 0x7f8d27a99df0 thread_stack 0x48000

(my_addr_resolve failure: fork)

/usr/sbin/mysqld(my_print_stacktrace+0x2e) [0x7f8d285e544e]

/usr/sbin/mysqld(handle_fatal_signal+0x457) [0x7f8d281145f7]

/lib/x86_64-linux-gnu/libpthread.so.0(+0x10340) [0x7f8d268b4340]

/usr/sbin/mysqld(Item_func_match::fix_index()+0x192) [0x7f8d28183712]

/usr/sbin/mysqld(setup_ftfuncs(st_select_lex*)+0x34) [0x7f8d27f3b314]

/usr/sbin/mysqld(JOIN::optimize()+0x294) [0x7f8d27fde334]

/usr/sbin/mysqld(handle_select(THD*, LEX*, select_result*, unsigned long)+0x2e5) [0x7f8d27fe32d5]

/usr/sbin/mysqld(+0x401c59) [0x7f8d27f7ac59]

/usr/sbin/mysqld(mysql_execute_command(THD*)+0x5d25) [0x7f8d27f8a4a5]

/usr/sbin/mysqld(+0x415feb) [0x7f8d27f8efeb]

/usr/sbin/mysqld(dispatch_command(enum_server_command, THD*, char*, unsigned int)+0x1fa1) [0x7f8d27f915f1]

/usr/sbin/mysqld(do_command(THD*)+0x28f) [0x7f8d27f922ff]

/usr/sbin/mysqld(do_handle_one_connection(THD*)+0x32b) [0x7f8d2806242b]

/usr/sbin/mysqld(handle_one_connection+0x40) [0x7f8d28062510]

/lib/x86_64-linux-gnu/libpthread.so.0(+0x8182) [0x7f8d268ac182]

/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d) [0x7f8d25fcf47d]

Trying to get some variables.

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

Query (0x7f8a6a064020): is an invalid pointer

Connection ID (thread ID): 26348

Status: NOT_KILLED

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

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

CREATE TABLE `fts_table` (

	`id` VARCHAR(255) NOT NULL COLLATE 'utf8_general_ci',

	`BUSINESS_NAME` TEXT NULL COLLATE 'utf8mb4_unicode_ci',

	`STREET_ADDRESS` TEXT NULL COLLATE 'utf8_unicode_ci',

	PRIMARY KEY (`id`),

	INDEX `name` (`BUSINESS_NAME`(191)),

	INDEX `addr` (`STREET_ADDRESS`(255)),

	FULLTEXT INDEX `ft` (`BUSINESS_NAME`),

	FULLTEXT INDEX `ft2` (`STREET_ADDRESS`)

)

COLLATE='utf8_unicode_ci'

ENGINE=InnoDB;

select * from fts_table where MATCH (BUSINESS_NAME, STREET_ADDRESS) AGAINST ('Some business name and address here');