mysqld got signal 11

Reproducable crash on simple update statement:

update relations set owner_id='name1' where owner_id='name2';

Possible cause are the OS updates, of which the following (Arch Linux) packages have been recently updated.

• adobe-source-serif-pro-fonts (2.007ro+1.007it-2 -> 2.010ro+1.010it-1)
• poppler (0.72.0-1 -> 0.73.0-1)
• cups-filters (1.21.6-1 -> 1.21.6-2)
• poppler-glib (0.72.0-1 -> 0.73.0-1)
• inkscape (0.92.4-1 -> 0.92.4-2)
• jre-openjdk-headless (11.0.1.u13-2 -> 11.0.2.u7-1)
• jre-openjdk (11.0.1.u13-2 -> 11.0.2.u7-1)
• jdk-openjdk (11.0.1.u13-2 -> 11.0.2.u7-1)
• jre8-openjdk-headless (8.u192-1 -> 8.u202-1)
• jre8-openjdk (8.u192-1 -> 8.u202-1)
• jdk8-openjdk (8.u192-1 -> 8.u202-1)
• libreoffice-fresh (6.1.4-2 -> 6.1.4-3)
• libsynctex (2018.48691-4 -> 2018.48691-5)
• libuv (1.24.1-1 -> 1.25.0-1)
• openjdk-doc (11.0.1.u13-2 -> 11.0.2.u7-1)
• openjdk-src (11.0.1.u13-2 -> 11.0.2.u7-1)
• openjdk8-doc (8.u192-1 -> 8.u202-1)
• openjdk8-src (8.u192-1 -> 8.u202-1)
• poppler-qt5 (0.72.0-1 -> 0.73.0-1)

Jan 20 21:36:50 z97 systemd[1]: Starting MariaDB 10.3.12 database server...
Jan 20 21:36:51 z97 mysqld[4740]: 2019-01-20 21:36:51 0 [Note] /usr/bin/mysqld (mysqld 10.3.12-MariaDB-log) starting as process 4740 ...
Jan 20 21:36:51 z97 mysqld[4740]: 2019-01-20 21:36:51 0 [Note] InnoDB: Using Linux native AIO
Jan 20 21:36:51 z97 mysqld[4740]: 2019-01-20 21:36:51 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
Jan 20 21:36:51 z97 mysqld[4740]: 2019-01-20 21:36:51 0 [Note] InnoDB: Uses event mutexes
Jan 20 21:36:51 z97 mysqld[4740]: 2019-01-20 21:36:51 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
Jan 20 21:36:51 z97 mysqld[4740]: 2019-01-20 21:36:51 0 [Note] InnoDB: Number of pools: 1
Jan 20 21:36:51 z97 mysqld[4740]: 2019-01-20 21:36:51 0 [Note] InnoDB: Using SSE2 crc32 instructions
Jan 20 21:36:51 z97 mysqld[4740]: 2019-01-20 21:36:51 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
Jan 20 21:36:51 z97 mysqld[4740]: 2019-01-20 21:36:51 0 [Note] InnoDB: Completed initialization of buffer pool
Jan 20 21:36:51 z97 mysqld[4740]: 2019-01-20 21:36:51 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
Jan 20 21:36:51 z97 mysqld[4740]: 2019-01-20 21:36:51 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=1115939382
Jan 20 21:36:51 z97 mysqld[4740]: 2019-01-20 21:36:51 0 [Note] InnoDB: Last binlog file './mysql-bin.000726', position 545
Jan 20 21:36:51 z97 mysqld[4740]: 2019-01-20 21:36:51 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
Jan 20 21:36:51 z97 mysqld[4740]: 2019-01-20 21:36:51 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
Jan 20 21:36:51 z97 mysqld[4740]: 2019-01-20 21:36:51 0 [Note] InnoDB: Creating shared tablespace for temporary tables
Jan 20 21:36:51 z97 mysqld[4740]: 2019-01-20 21:36:51 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
Jan 20 21:36:51 z97 mysqld[4740]: 2019-01-20 21:36:51 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
Jan 20 21:36:51 z97 mysqld[4740]: 2019-01-20 21:36:51 0 [Note] InnoDB: Waiting for purge to start
Jan 20 21:36:51 z97 mysqld[4740]: 2019-01-20 21:36:51 0 [Note] InnoDB: 10.3.12 started; log sequence number 1115939391; transaction id 2366970
Jan 20 21:36:51 z97 mysqld[4740]: 2019-01-20 21:36:51 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
Jan 20 21:36:51 z97 mysqld[4740]: 2019-01-20 21:36:51 0 [Note] Recovering after a crash using mysql-bin
Jan 20 21:36:51 z97 mysqld[4740]: 2019-01-20 21:36:51 0 [Note] InnoDB: Buffer pool(s) load completed at 190120 21:36:51
Jan 20 21:36:51 z97 mysqld[4740]: 2019-01-20 21:36:51 0 [Note] Starting crash recovery...
Jan 20 21:36:51 z97 mysqld[4740]: 2019-01-20 21:36:51 0 [Note] Crash recovery finished.
Jan 20 21:36:51 z97 mysqld[4740]: 2019-01-20 21:36:51 0 [Note] Server socket created on IP: '::'.
Jan 20 21:36:51 z97 mysqld[4740]: 2019-01-20 21:36:51 0 [Note] Reading of all Master_info entries succeded
Jan 20 21:36:51 z97 mysqld[4740]: 2019-01-20 21:36:51 0 [Note] Added new Master_info '' to hash table
Jan 20 21:36:51 z97 mysqld[4740]: 2019-01-20 21:36:51 0 [Note] /usr/bin/mysqld: ready for connections.
Jan 20 21:36:51 z97 mysqld[4740]: Version: '10.3.12-MariaDB-log' socket: '/run/mysqld/mysqld.sock' port: 3306 Source distribution
Jan 20 21:36:51 z97 systemd[1]: Started MariaDB 10.3.12 database server.
Jan 20 21:39:29 z97 mysqld[4740]: 190120 21:39:29 [ERROR] mysqld got signal 11 ;
Jan 20 21:39:29 z97 mysqld[4740]: This could be because you hit a bug. It is also possible that this binary
Jan 20 21:39:29 z97 mysqld[4740]: or one of the libraries it was linked against is corrupt, improperly built,
Jan 20 21:39:29 z97 mysqld[4740]: or misconfigured. This error can also be caused by malfunctioning hardware.
Jan 20 21:39:29 z97 mysqld[4740]: To report this bug, see https://mariadb.com/kb/en/reporting-bugs
Jan 20 21:39:29 z97 mysqld[4740]: We will try our best to scrape up some info that will hopefully help
Jan 20 21:39:29 z97 mysqld[4740]: diagnose the problem, but since we have already crashed,
Jan 20 21:39:29 z97 mysqld[4740]: something is definitely wrong and this may fail.
Jan 20 21:39:29 z97 mysqld[4740]: Server version: 10.3.12-MariaDB-log
Jan 20 21:39:29 z97 mysqld[4740]: key_buffer_size=16777216
Jan 20 21:39:29 z97 mysqld[4740]: read_buffer_size=262144
Jan 20 21:39:29 z97 mysqld[4740]: max_used_connections=21
Jan 20 21:39:29 z97 mysqld[4740]: max_threads=153
Jan 20 21:39:29 z97 mysqld[4740]: thread_count=28
Jan 20 21:39:29 z97 mysqld[4740]: It is possible that mysqld could use up to
Jan 20 21:39:29 z97 mysqld[4740]: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 137277 K bytes of memory
Jan 20 21:39:29 z97 mysqld[4740]: Hope that's ok; if not, decrease some variables in the equation.
Jan 20 21:39:29 z97 mysqld[4740]: Thread pointer: 0x7f566a8810c8
Jan 20 21:39:29 z97 mysqld[4740]: Attempting backtrace. You can use the following information to find out
Jan 20 21:39:29 z97 mysqld[4740]: where mysqld died. If you see no messages after this, something went
Jan 20 21:39:29 z97 mysqld[4740]: terribly wrong...
Jan 20 21:39:29 z97 mysqld[4740]: stack_bottom = 0x7f566dbad5f8 thread_stack 0x49000

No errors in dmesg.