MySQL Bugs: #71023: InnoDB crashes (purge reached the head of the history list...)

Bug #71023	InnoDB crashes (purge reached the head of the history list...)
Submitted:	27 Nov 2013 11:16	Modified:	2 Jan 2014 17:06
Reporter:	Rolf Moholth	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Server: InnoDB storage engine	Severity:	S1 (Critical)
Version:	MySQL Server 5.5	OS:	Windows (Server 2008 R2 Standard)
Assigned to:		CPU Architecture:	Any
Tags:	crash, MySQL Server 5.5

Description:
Note: This might very well be a duplicate of Bug #31123, but it is still very much alive and kicking! We have observed it twice within a month on different servers.

The following error is reported repeatedly:

131127 10:54:49 InnoDB: Warning: purge reached the head of the history list,
InnoDB: but its length is still reported as 76217726! Make a detailed bug
InnoDB: report, and submit it to http://bugs.mysql.com
...

After a while, the server seems satisified with the dismal state of things and terminates with the following message:

131127 10:54:54 InnoDB: Assertion failure in thread 776 in file trx0trx.c line 407
InnoDB: Failing assertion: (trx_sys->mysql_trx_list).count > 0
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.5/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
InnoDB: Thread 6024 stopped in file sync0arr.c line 359
InnoDB: Thread 2088 stopped in file ut0ut.c line 76
InnoDB: Thread 2068 stopped in file sync0arr.c line 359
InnoDB: Thread 2072 stopped in file os0sync.c line 781
InnoDB: Thread 5460 stopped in file ha_innodb.cc line 7855

How to repeat:
Spurious crash. As far as we know, it cannot be willfully repeated, but a quick google gives me the definite impression that this is a very frequent bug?

Thank you for the report.

Please specify exact minor version of MySQL server you use and upload full error log file.

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".