Version: '10.3.8-MariaDB-valgrind-max-debug-log'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  Source distribution
2018-09-18 21:47:29 0 [Note] Got signal 15 to shutdown mysqld
2018-09-18 21:47:29 0 [Note] /usr/local/mysql/bin/mysqld (initiated by: root[root] @ localhost []): Normal shutdown
2018-09-18 21:47:29 0 [Note] InnoDB: FTS optimize thread exiting.
2018-09-18 21:47:29 0 [Note] Event Scheduler: Purging the queue. 0 events
mysqld: /mariadb/sql/sql_list.h:631: void ilink::assert_linked(): Assertion `prev != 0 && next != 0' failed.
mysqld: /mariadb/sql/sql_list.h:631: void ilink::assert_linked(): Assertion `prev != 0 && next != 0' failed.
mysqld: /mariadb/sql/sql_list.h:631: void ilink::assert_linked(): Assertion `prev != 0 && next != 0' failed.
180918 21:47:57 [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
==1==
==1== Process terminating with default action of signal 6 (SIGABRT): dumping core
==1==    at 0x6D54277: raise (in /usr/lib64/libc-2.17.so)
==1==    by 0x6D55967: abort (in /usr/lib64/libc-2.17.so)
==1==    by 0x6D4D095: __assert_fail_base (in /usr/lib64/libc-2.17.so)
==1==    by 0x6D4D141: __assert_fail (in /usr/lib64/libc-2.17.so)
==1==    by 0x653DA1: ilink::assert_linked() (sql_list.h:631)
==1==    by 0x655271: unlink_not_visible_thd(THD*) (sql_class.h:4849)
==1==    by 0x70A4C4: destroy_thd(THD*) (sql_class.cc:4726)
==1==    by 0xE5C840: thd_destructor_proxy (ha_innodb.cc:330)
==1==    by 0x4E34E24: start_thread (in /usr/lib64/libpthread-2.17.so)
==1==    by 0x6E1CBAC: clone (in /usr/lib64/libc-2.17.so)
valgrind: m_mallocfree.c:307 (get_bszB_as_is): Assertion 'bszB_lo == bszB_hi' failed.
valgrind: Heap block lo/hi size mismatch: lo = 1, hi = 4294967295.
This is probably caused by your program erroneously writing past the
end of a heap block and corrupting heap metadata.  If you fix any
invalid writes reported by Memcheck, this assertion failure will
probably go away.  Please try that before reporting this as a bug.
host stacktrace:
==1==    at 0x5800F3DD: ??? (in /usr/lib64/valgrind/massif-amd64-linux)
==1==    by 0x5800F4F4: ??? (in /usr/lib64/valgrind/massif-amd64-linux)
==1==    by 0x5800F681: ??? (in /usr/lib64/valgrind/massif-amd64-linux)
==1==    by 0x5801C66D: ??? (in /usr/lib64/valgrind/massif-amd64-linux)
==1==    by 0x580627C7: ??? (in /usr/lib64/valgrind/massif-amd64-linux)
==1==    by 0x58013FB7: ??? (in /usr/lib64/valgrind/massif-amd64-linux)
==1==    by 0x580140EC: ??? (in /usr/lib64/valgrind/massif-amd64-linux)
==1==    by 0x580711C1: ??? (in /usr/lib64/valgrind/massif-amd64-linux)
==1==    by 0x5807130A: ??? (in /usr/lib64/valgrind/massif-amd64-linux)
==1==    by 0x5809A50D: ??? (in /usr/lib64/valgrind/massif-amd64-linux)
==1==    by 0xDEADBEEFDEADBEEE: ???
sched status:
  running_tid=38
Thread 38: status = VgTs_Runnable (lwpid 59)
==1==    at 0x4C290CD: free (vg_replace_malloc.c:530)
==1==    by 0x6E8E26B: __libc_freeres (in /usr/lib64/libc-2.17.so)
==1==    by 0x4A24749: _vgnU_freeres (vg_preloaded.c:77)
==1==    by 0x6D55967: abort (in /usr/lib64/libc-2.17.so)
==1==    by 0x6D4D095: __assert_fail_base (in /usr/lib64/libc-2.17.so)
==1==    by 0x6D4D141: __assert_fail (in /usr/lib64/libc-2.17.so)
==1==    by 0x653DA1: ilink::assert_linked() (sql_list.h:631)
==1==    by 0x655271: unlink_not_visible_thd(THD*) (sql_class.h:4849)
==1==    by 0x70A4C4: destroy_thd(THD*) (sql_class.cc:4726)
==1==    by 0xE5C840: thd_destructor_proxy (ha_innodb.cc:330)
==1==    by 0x4E34E24: start_thread (in /usr/lib64/libpthread-2.17.so)
==1==    by 0x6E1CBAC: clone (in /usr/lib64/libc-2.17.so)
Note: see also the FAQ in the source distribution.
It contains workarounds to several common problems.
In particular, if Valgrind aborted or crashed after
identifying problems in your program, there's a good chance
that fixing those problems will prevent Valgrind aborting or
crashing, especially if it happened in m_mallocfree.c.
If that doesn't help, please report this bug to: www.valgrind.org
In the bug report, send all the above text, the valgrind
version, and what OS and version you are using.  Thanks.