Bug #57539 "Error: semaphore wait has lasted > 600 seconds" leads to server crash
Submitted: 18 Oct 2010 20:16 Modified: 25 Oct 2010 8:26
Reporter: Roel Van de Paar Email Updates:
Status: Duplicate Impact on me:
Category:MySQL Server: InnoDB storage engine Severity:S2 (Serious)
Version:5.1.47 OS:Windows
Assigned to: CPU Architecture:Any

[18 Oct 2010 20:16] Roel Van de Paar
InnoDB: Error: semaphore wait has lasted > 600 seconds
InnoDB: We intentionally crash the server, because it appears to be hung.
100908 10:15:34  InnoDB: Assertion failure in thread 2704 in file .\srv\srv0srv.c line 2232
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.1/en/forcing-recovery.html
InnoDB: about forcing recovery.
100908 10:15:34 - mysqld got exception 0xc0000005 ;

How to repeat:
[25 Oct 2010 8:26] Roel Van de Paar
Decided to mark this as duplicate of Bug #57579 - "blobs cause a thread to wait for itself endlessly, before long semaphore death" ftm.