Comment 13 for bug 1729536

I reactivated one set of optimize queries for this night and it crashed with the exact same backtrace. So I can confirm this is indeed related to this specific set. However, there is nothing fancy about them at all.

It is a simple SQL script with 9 OPTIMIZE statements being run from the mysql client (CLI) on a single database.
OPTIMIZE TABLE Table1;
OPTIMIZE TABLE Table2;
OPTIMIZE TABLE Table3;
...

When executing the queries manually, one by one, all work.
When executing the queries from an sql script via the mysql client (CLI), all works.

I would tend to believe that it must be linked to some execution context. The only thing I can think of is concurrent queries being run at the same time ... but again, in our case, the crash occurs on a slave server running queries from its master only. In this configuration, there should not be anything like a concurrent query I believe ? Only binlog entries being read one by one and applied ?