MySQL restarted after failed creating FK

2014-11-19 09:36:46 7f148ef22700  InnoDB: Assertion failure in thread 139726274307840 in file dict0mem.h line 1165

InnoDB: Failing assertion: ret.second

InnoDB: We intentionally generate a memory trap.

InnoDB: Submit a detailed bug report to http://bugs.mysql.com.

InnoDB: If you get repeated assertion failures or crashes, even

InnoDB: immediately after the mysqld startup, there may be

InnoDB: corruption in the InnoDB tablespace. Please refer to

InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html

InnoDB: about forcing recovery.

141119  9:36:46 [ERROR] mysqld got signal 6 ;

This could be because you hit a bug. It is also possible that this binary

or one of the libraries it was linked against is corrupt, improperly built,

or misconfigured. This error can also be caused by malfunctioning hardware.

ALTER TABLE

  `PROD_ATTENTE_CONFIGURATION_IMPOSITION`

ADD

  FOREIGN KEY (`ID_PROD_COMMANDE`) REFERENCES `PRODUCTION`.`PROD_COMMANDES`(`ID_PROD_COMMANDE`) ON DELETE RESTRICT ON UPDATE RESTRICT;

Warning: mysqli_query(): MySQL server has gone away in /data/www/photobox/vendor/glial/glial/Glial/Sgbd/Sql/Mysql/Mysql.php on line 91

Warning: mysqli_query(): Error reading result set's header in /data/www/photobox/vendor/glial/glial/Glial/Sgbd/Sql/Mysql/Mysql.php on line 91

SQL : ALTER TABLE `PROD_ATTENTE_CONFIGURATION_IMPOSITION` ADD FOREIGN KEY (`ID_PROD_COMMANDE`) REFERENCES `PRODUCTION`.`PROD_COMMANDES`(`ID_PROD_COMMANDE`) ON DELETE RESTRICT ON UPDATE RESTRICT;

MySQL server has gone away