180410 17:15:18 [ERROR] mysqld got signal 8 ;

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.2.13-MariaDB-10.2.13+maria~trusty-log

key_buffer_size=16777216

read_buffer_size=1073741824

max_used_connections=256

max_threads=402

thread_count=136

It is possible that mysqld could use up to 

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

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

Thread pointer: 0x0

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 = 0x0 thread_stack 0x30000

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

/usr/sbin/mysqld(handle_fatal_signal+0x355)[0x555d09ef7295]

/lib/x86_64-linux-gnu/libpthread.so.0(+0x10330)[0x7f9c599b9330]

/usr/sbin/mysqld(+0xa08219)[0x555d0a28e219]

/lib/x86_64-linux-gnu/libpthread.so.0(+0x8184)[0x7f9c599b1184]

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

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.