2019-02-19 13:50:36 140614250160704 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2019-02-19 13:50:36 140614250160704 [Note] InnoDB: The InnoDB memory heap is disabled
2019-02-19 13:50:36 140614250160704 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2019-02-19 13:50:36 140614250160704 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2019-02-19 13:50:36 140614250160704 [Note] InnoDB: Compressed tables use zlib 1.2.8
2019-02-19 13:50:36 140614250160704 [Note] InnoDB: Using Linux native AIO
2019-02-19 13:50:36 140614250160704 [Note] InnoDB: Using SSE crc32 instructions
2019-02-19 13:50:36 140614250160704 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2019-02-19 13:50:36 140614250160704 [Note] InnoDB: Completed initialization of buffer pool
2019-02-19 13:50:36 140614250160704 [Note] InnoDB: Highest supported file format is Barracuda.
2019-02-19 13:50:36 140614250160704 [Note] InnoDB: Starting crash recovery from checkpoint LSN=589782303912
2019-02-19 13:50:36 140614250160704 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer...
InnoDB: 1 transaction(s) which must be rolled back or cleaned up
InnoDB: in total 0 row operations to undo
InnoDB: Trx id counter is 331034368
2019-02-19 13:50:36 140614250160704 [Note] InnoDB: Starting final batch to recover 101 pages from redo log
2019-02-19 13:50:36 140614250160704 [Note] InnoDB: 128 rollback segment(s) are active.
2019-02-19 13:50:36 140613693466368 [Note] InnoDB: Starting in background the rollback of recovered transactions
2019-02-19 13:50:36 7fe32d3fe700  InnoDB: Rolling back trx with id 331032999, 0 rows to undo
2019-02-19 13:50:36 7fe32d3fe700  InnoDB: Assertion failure in thread 140613693466368 in file fut0lst.ic line 83
InnoDB: Failing assertion: addr.page == FIL_NULL || addr.boffset >= FIL_PAGE_DATA
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.
2019-02-19 13:50:36 140614250160704 [Note] InnoDB: Waiting for purge to start
190219 13:50:36 [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.26-MariaDB-0+deb9u1
key_buffer_size=16777216
read_buffer_size=131072
max_used_connections=0
max_threads=153
thread_count=0
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 352445 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)[0x55cb4bee536e]
/usr/sbin/mysqld(handle_fatal_signal+0x3bd)[0x55cb4ba2aa4d]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x110c0)[0x7fe34e3550c0]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0xcf)[0x7fe34cc4ffff]
2019-02-19 13:50:36 140614250160704 [Note] InnoDB:  Percona XtraDB (http://www.percona.com) 5.6.36-82.1 started; log sequence number 589782326827
/lib/x86_64-linux-gnu/libc.so.6(abort+0x16a)[0x7fe34cc5142a]
/usr/sbin/mysqld(+0x36034b)[0x55cb4b7e834b]
/usr/sbin/mysqld(+0x9eb431)[0x55cb4be73431]
/usr/sbin/mysqld(+0x9153fb)[0x55cb4bd9d3fb]
/usr/sbin/mysqld(+0x930303)[0x55cb4bdb8303]
/usr/sbin/mysqld(+0x926a3e)[0x55cb4bdaea3e]
/usr/sbin/mysqld(+0x927ee0)[0x55cb4bdafee0]
/usr/sbin/mysqld(+0x91f07d)[0x55cb4bda707d]
/usr/sbin/mysqld(+0x91f771)[0x55cb4bda7771]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x7494)[0x7fe34e34b494]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x3f)[0x7fe34cd05acf]
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.