Comment 6 for bug 1154558

It didn't hang for about two days with the switched off lazy drop table. Nevertheless I think it passed too little time to make any conclusions that switching off this option has really helped. With lazy_drop on it could either work without crashing for about three days or hang three times a day.
I took a closer look at log spool queue of tasks executing and it really had a command for database dropping before failure.

> 2013-03-11 23:47:14 zernplus drop mySQL gb_x_zernplus (server 77)

130311 23:25:34 [ERROR] /opt/mysql+/5.5.29-rel30.0-451/bin/mysqld: Table './gb_gazrs/cms_online' is marked as crashed and last (automatic?) repair failed
InnoDB: Error: Waited for 5 secs for hash index ref_count (3) to drop to 0.
index: "PRIMARY" table: "gb_x_zernplus/c8qey_extensions"

So I keep on waiting.
Thank you for your answers.