Had this issue on one site when running Chrome and after much hunting did not find a documented solution. However I did manage to find and correct the issue after a little playing with my code.

The issue ended up being a totally unrelated

Innodb tables are tables within MySQL that should be used instead of MyISAM for numerous reasons, the very least is that their transactional nature means they will not corrupt if you system has to reboot or lose power.

One of the problems is to change your tables from MyISAM to Innodb you need to run the following command:
ALTER TABLE YourDB.wp_posts ENGINE=InnoDB;
Once per table and that means lots of manual typing

I found a script that will create the list of tables for you:
SELECT CONCAT( 'ALTER TABLE `', table_schema, '`.`', table_name, '` ENGINE=InnoDB;' )
FROM information_schema.tables
WHERE ENGINE = 'MyISAM'
AND table_schema NOT
IN (
'information_schema', 'mysql'
)

Which outputs something like:
ALTER TABLE YourDB.wp_bad_behavior… Read the rest