Comment 4 for bug 934377

Thanks for the followup, we'll try that.

- Chris Clifton

On Sat, Nov 10, 2012 at 4:44 AM, Laurynas Biveinis <
<email address hidden>> wrote:

> Chris -
>
> The issue you are experiencing could be bug 1042640, which is fixed in
> 5.5.28-29.1. Please upgrade and check if you can reproduce the issue
> then. Thanks!
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/934377
>
> Title:
> Crash in insert benchmark
>
> Status in Percona Server with XtraDB:
> Incomplete
>
> Bug description:
> In some insert intensive benchmark I've got crash
> Version: '5.5.20-rel24.1-log' socket: '/var/lib/mysql/mysql.sock'
> port: 3306 Percona Server with XtraDB (GPL), Release rel24.1, Revision 217
> 120217 9:52:09 InnoDB: Assertion failure in thread 140660403742464 in
> file buf0flu.c line 542
> InnoDB: Failing assertion: (buf_pool->flush_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.
>
>
> I do not have reliable procedure to repeat, but I will update ticket
> when I have more information.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/percona-server/+bug/934377/+subscriptions
>