11:27:48.380 [Exec Stream Pumper] ERROR ch.vorburger.exec.ManagedProcess - mysqld: *** set a breakpoint in malloc_error_break to debug

11:27:48.380 [Exec Stream Pumper] ERROR ch.vorburger.exec.ManagedProcess - mysqld: 180726 11:27:48 [ERROR] mysqld got signal 6 ;

11:27:48.380 [Exec Stream Pumper] INFO ch.vorburger.exec.ManagedProcess - mysqld: This could be because you hit a bug. It is also possible that this binary

11:27:48.380 [Exec Stream Pumper] INFO ch.vorburger.exec.ManagedProcess - mysqld: or one of the libraries it was linked against is corrupt, improperly built,

11:27:48.380 [Exec Stream Pumper] ERROR ch.vorburger.exec.ManagedProcess - mysqld: or misconfigured. This error can also be caused by malfunctioning hardware.

11:27:48.380 [Exec Stream Pumper] INFO ch.vorburger.exec.ManagedProcess - mysqld: 

11:27:48.380 [Exec Stream Pumper] INFO ch.vorburger.exec.ManagedProcess - mysqld: To report this bug, see https://mariadb.com/kb/en/reporting-bugs

11:27:48.380 [Exec Stream Pumper] INFO ch.vorburger.exec.ManagedProcess - mysqld: 

11:27:48.380 [Exec Stream Pumper] INFO ch.vorburger.exec.ManagedProcess - mysqld: We will try our best to scrape up some info that will hopefully help

11:27:48.380 [Exec Stream Pumper] INFO ch.vorburger.exec.ManagedProcess - mysqld: diagnose the problem, but since we have already crashed, 

11:27:48.380 [Exec Stream Pumper] INFO ch.vorburger.exec.ManagedProcess - mysqld: something is definitely wrong and this may fail.

11:27:48.380 [Exec Stream Pumper] INFO ch.vorburger.exec.ManagedProcess - mysqld: 

11:27:48.380 [Exec Stream Pumper] INFO ch.vorburger.exec.ManagedProcess - mysqld: Server version: 10.2.11-MariaDB

11:27:48.380 [Exec Stream Pumper] INFO ch.vorburger.exec.ManagedProcess - mysqld: key_buffer_size=134217728

11:27:48.380 [Exec Stream Pumper] INFO ch.vorburger.exec.ManagedProcess - mysqld: read_buffer_size=131072

11:27:48.380 [Exec Stream Pumper] INFO ch.vorburger.exec.ManagedProcess - mysqld: max_used_connections=3

11:27:48.380 [Exec Stream Pumper] INFO ch.vorburger.exec.ManagedProcess - mysqld: max_threads=153

11:27:48.380 [Exec Stream Pumper] INFO ch.vorburger.exec.ManagedProcess - mysqld: thread_count=9

11:27:48.380 [Exec Stream Pumper] INFO ch.vorburger.exec.ManagedProcess - mysqld: It is possible that mysqld could use up to 

11:27:48.380 [Exec Stream Pumper] INFO ch.vorburger.exec.ManagedProcess - mysqld: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467247 K  bytes of memory

11:27:48.380 [Exec Stream Pumper] INFO ch.vorburger.exec.ManagedProcess - mysqld: Hope that's ok; if not, decrease some variables in the equation.

11:27:48.380 [Exec Stream Pumper] INFO ch.vorburger.exec.ManagedProcess - mysqld: 

11:27:48.380 [Exec Stream Pumper] INFO ch.vorburger.exec.ManagedProcess - mysqld: Thread pointer: 0x7fee7e02f808

11:27:48.380 [Exec Stream Pumper] INFO ch.vorburger.exec.ManagedProcess - mysqld: Attempting backtrace. You can use the following information to find out

11:27:48.380 [Exec Stream Pumper] INFO ch.vorburger.exec.ManagedProcess - mysqld: where mysqld died. If you see no messages after this, something went

11:27:48.380 [Exec Stream Pumper] INFO ch.vorburger.exec.ManagedProcess - mysqld: terribly wrong...