First of all, this does not seem to be necessary at all when XtraDB-specific innodb_show_verbose_locks is 0 (which it is in this case).
Second, the buffer page read happens with no locks held, thus the read must handle everything, including a disappearing page, which is the cause of this crash. The latter seems to apply to InnoDB too.
lock_print_ info_all_ transactions attempts to load a buffer page for a possible eventual detailed lock dump:
lock_ mutex_exit_ kernel( );
mtr_start(&mtr);
buf_ page_get_ with_no_ latch(space, zip_size,
page_no, &mtr);
mtr_ commit( &mtr);
load_page_first = FALSE;
lock_ mutex_enter_ kernel( );
First of all, this does not seem to be necessary at all when XtraDB-specific innodb_ show_verbose_ locks is 0 (which it is in this case).
Second, the buffer page read happens with no locks held, thus the read must handle everything, including a disappearing page, which is the cause of this crash. The latter seems to apply to InnoDB too.