mysqld got signal 11

• In the middle of the day, when use is actually low (we run massive updates over night and machine is quite a bit more busy then with many threads going), mariadb died. CPU use was around 12% on one core by mariadb at the time. No idea from the log why, so, including here. From reading the info, it would appear there is no dump, right? I see no reference to any fix in 10.1.29.

mysqld would have been started with the following arguments:
--datadir=/var/lib/mysql --socket=/var/lib/mysql/mysql.sock --pid-file=/var/run/mariadb/mariadb.pid --symbolic-links=0 --innodb_file_per_table=1 --datadir=/home/mysql --socket=/var/lib/mysql/mysql.sock --tmpdir=/home/mysqltemp --log-bin=/var/lib/mysqllogs/binlog --expire_logs_days=3 --log_error=/var/log/mariadb/mariadb.log --slow_query_log=1 --slow_query_log_file=/var/log/mariadb/slow-query.log --long_query_time=30 --log_slow_admin_statements=1 --user=mysql --binlog-format=MIXED --collation_server=latin1_general_cs --group_concat_max_len=2M --server_id=9 --slave_compressed_protocol=1 --symbolic-links=0 --max_connections=250 --thread_handling=pool-of-threads --extra_port=3307 --connect_timeout=50 --max_heap_table_size=512M --tmp_table_size=512M --max_allowed_packet=64M --query_cache_size=128M --query_prealloc_size=499712 --net_read_timeout=300 --net_write_timeout=600 --table_open_cache=10000 --innodb_flush_log_at_trx_commit=0 --innodb_log_file_size=1G --innodb_buffer_pool_size=24G --innodb_lock_wait_timeout=500 --innodb_flush_method=O_DIRECT --innodb_file_format=Barracuda --innodb_status_output=0 --innodb_status_output_locks=1 --innodb_stats_sample_pages=12 --innodb_read_io_threads=8 --key_buffer_size=256M --join_buffer_size=512K --bulk_insert_buffer_size=512M --read_rnd_buffer_size=1M --aria_pagecache_buffer_size=512M --aria_sort_buffer_size=256M