Crash on creating large FULLTEXT index

161014 13:56:15 [ERROR] 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.

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.18-MariaDB-1~xenial

key_buffer_size=402653184

read_buffer_size=2097152

max_used_connections=1

max_threads=153

thread_count=1

It is possible that mysqld could use up to

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

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

Thread pointer: 0x0x6ffce008

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

(my_addr_resolve failure: fork)

/usr/sbin/mysqld(my_print_stacktrace+0x28) [0xb69fbe28]

/usr/sbin/mysqld(handle_fatal_signal+0x2c7) [0xb652d777]

[0xb6eb8404]

[0xb6eb8428]

/lib/i386-linux-gnu/libc.so.6(gsignal+0x39) [0xb597ce89]

/lib/i386-linux-gnu/libc.so.6(abort+0x157) [0xb597e3e7]

/usr/sbin/mysqld(+0x57c5a7) [0xb66975a7]

/usr/sbin/mysqld(+0x5d16fd) [0xb66ec6fd]

/usr/sbin/mysqld(+0x6194ef) [0xb67344ef]

/usr/sbin/mysqld(+0x61ad8f) [0xb6735d8f]

/usr/sbin/mysqld(+0x6202df) [0xb673b2df]

/usr/sbin/mysqld(+0x58547d) [0xb66a047d]

/usr/sbin/mysqld(mysql_alter_table(THD*, char*, char*, HA_CREATE_INFO*, TABLE_LIST*, Alter_info*, unsigned int, st_order*, bool)+0x2ef7) [0xb6422a57]

/usr/sbin/mysqld(mysql_execute_command(THD*)+0x7ce7) [0xb6393037]

/usr/sbin/mysqld(mysql_parse(THD*, char*, unsigned int, Parser_state*)+0x320) [0xb6396160]

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

/usr/sbin/mysqld(do_command(THD*)+0x1b4) [0xb639a7d4]

/usr/sbin/mysqld(do_handle_one_connection(THD*)+0x1ec) [0xb6468c4c]

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

/lib/i386-linux-gnu/libpthread.so.0(+0x62b5) [0xb5d682b5]

/lib/i386-linux-gnu/libc.so.6(clone+0x6e) [0xb5a3816e]

Trying to get some variables.

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

Query (0x67819018): is an invalid pointer

Connection ID (thread ID): 2

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=o$

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.

We think the query pointer is invalid, but we will try to print it anyway.

Query: CREATE FULLTEXT INDEX `fullemail` ON `contacts` (`email`)

161014 13:56:16 mysqld_safe Number of processes running now: 0

161014 13:56:16 mysqld_safe mysqld restarted

2016-10-14 13:56:16 3044911104 [Note] /usr/sbin/mysqld (mysqld 10.1.18-MariaDB-1~xenial) starting as process 8594 ...

2016-10-14 13:56:17 b57da800 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory alloc$

2016-10-14 13:56:17 3044911104 [Note] InnoDB: Using mutexes to ref count buffer pool pages

2016-10-14 13:56:17 3044911104 [Note] InnoDB: The InnoDB memory heap is disabled

2016-10-14 13:56:17 3044911104 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins

2016-10-14 13:56:17 3044911104 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier

2016-10-14 13:56:17 3044911104 [Note] InnoDB: Compressed tables use zlib 1.2.8

2016-10-14 13:56:17 3044911104 [Note] InnoDB: Using Linux native AIO

2016-10-14 13:56:18 3044911104 [Note] InnoDB: Using generic crc32 instructions

2016-10-14 13:56:18 3044911104 [Note] InnoDB: Initializing buffer pool, size = 384.0M

2016-10-14 13:56:18 3044911104 [Note] InnoDB: Completed initialization of buffer pool

2016-10-14 13:56:18 3044911104 [Note] InnoDB: Highest supported file format is Barracuda.

2016-10-14 13:56:18 3044911104 [Note] InnoDB: The log sequence numbers 385048524300 and 385048524300 in ibdata files do not match the log sequence number 385408285912 in the ib_logfiles!

2016-10-14 13:56:18 3044911104 [Note] InnoDB: Database was not shutdown normally!

2016-10-14 13:56:18 3044911104 [Note] InnoDB: Starting crash recovery.

2016-10-14 13:56:18 3044911104 [Note] InnoDB: Reading tablespace information from the .ibd files...

2016-10-14 13:56:21 3044911104 [Note] InnoDB: Restoring possible half-written data pages

2016-10-14 13:56:21 3044911104 [Note] InnoDB: from the doublewrite buffer...

InnoDB: Last MySQL binlog file position 0 1215194, file name /var/log/mysql/mariadb-bin.000024

2016-10-14 13:56:22 3044911104 [Note] InnoDB: 128 rollback segment(s) are active.

2016-10-14 13:56:22 3044911104 [Note] InnoDB: Waiting for purge to start

2016-10-14 13:56:22 3044911104 [Note] InnoDB:  Percona XtraDB (http://www.percona.com) 5.6.32-78.1 started; log sequence number 385408285912

2016-10-14 13:56:22 1799355200 [Note] InnoDB: Dumping buffer pool(s) not yet started

2016-10-14 13:56:22 3044911104 [Note] Plugin 'FEEDBACK' is disabled.

2016-10-14 13:56:22 3044911104 [Note] Recovering after a crash using tc.log

2016-10-14 13:56:22 3044911104 [Note] Starting crash recovery...

2016-10-14 13:56:22 3044911104 [Note] Crash recovery finished.

2016-10-14 13:56:22 3044911104 [Note] Server socket created on IP: '::'.

2016-10-14 13:56:23 3044911104 [Note] /usr/sbin/mysqld: ready for connections.

Version: '10.1.18-MariaDB-1~xenial'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  mariadb.org binary distribution