MariaDB Crashes after transactions locked due to semasphore and subsequent attempted blocking transaction rollback (kill)

I have quite a few transations, inserts, update's etc. on one of our tables from multiple clusters. I was monitoring the server and noticed that it became unresponsive to transactions, so I checked the processlist and saw that transactions were backing up.

I captured an 'show engine innodb status' and then attempted to kill (rollback) the blocking 'update' transaction. Within a minute the server crashed and rebooted.

Server is currently participating in async replication with three additional servers. Been quite pleased with the performance.

I will attach the mariadb.log and the show_engine_innodb_status output as separate files.

I'm working at fixing those unsafe binary log transactions. Not sure if that has anything to do with the crash.