Core dump after upgrade from MySQL 5.0 and start replication

We are in the process of upgrading many MySQL 5.0.90 database servers to MariaDB 10.2.8. Our process has been working: Copy the data from MySQL 5.0 to the maraidb server, upgrade -> 5.1 -> 5.5 -> MariaDB. We then run replication from MySQL 5.0 to MariaDB using statement based replication for a period of time before moving the processing over to MariaDB.

The more detailed process goes as follows: Stop the slave on the source (MySQL 5.0.90) server. Rsync the entire data dir to the target (maria 10.2.8) server. Start MySQL 5.0 on the target server and get replication caught up. Stop MySQL 5.0 on the target and start MySQL 5.1. Run mysql_upgrade. Stop MySQL 5.1. Start replication and let it catch up. Run MySQL 5.5 and perform upgrade. start replication and let it catch up. Stop MySQL 5.5. Run MariaDB 10.2.8 and perform upgrade. Start replication and let it catch up.

This has worked numerous times. However The latest attempt core dumps on the last step (replication from 5.0 to 10.2) before replication even catches up.

When I mysqldump the data in MySQL 5.0 and then import it directly to MariaDB it works fine, but it is so slow it is impractical for large data sets.