Comment 4 for bug 1391660

I am not using GTIDs but this bug seem to have bitten me right away.
Entire INNODB subsystem locked , with main thread as a blocker (holding a lock), in state: enforcing dict cache limit.
After 600 seconds InnoDB surrendered with an assertion, and server was restarted my mysqld_safe.

Looking at the error log, what puzzles me is the following (139627810412288 is the main thread, the blocker):

--Thread 139627810412288 has waited at srv0srv.cc line 2596 for 241.00 seconds the semaphore:
X-lock (wait_ex) on RW-latch at 0x134c460 '&dict_operation_lock'
a writer (thread id 139627810412288) has reserved it in mode wait exclusive
number of readers 7, waiters flag 1, lock_word: fffffffffffffff9
Last time read locked in file row0ins.cc line 1803
Last time write locked in file /mnt/workspace/percona-server-5.6-redhat-binary/label_exp/centos6-64/rpmbuild/BUILD/percona-server-5.6.25-73.1/storage/innobase/dict/dict0stats.cc line 2385

So, from the above it seems that the blocker was blocked by itself. This seems quite odd!!

Any thoughts?

Running Percona Server 5.6.25-73.1-log .

Thanks
Rick