Saw 10 out of 50 threads ut_ad simultaneously on unmodified code. Log buffer size = 10M, log file size = 10.

013-10-31 15:01:42 10d80f0002013-10-31 15:01:42 10d0930002013-10-31 15:01:42 10de2d0002013-10-31 15:01:42 10d9e40002013-10-31 15:01:42 10d8950002013-10-31 15:01:42 10d00d0002013-10-31 15:01:42 10d0500002013-10-31 15:01:42 10d7030002013-10-31 15:01:42 10d0d60002013-10-31 15:01:42 10da270002013-10-31 15:01:42 10d4eb000  InnoDB: Assertion failure in thread 4521521152 in file log0log.cc line 308
  InnoDB: Assertion failure in thread 4513673216 in file log0log.cc line 308
  InnoDB: Assertion failure in thread 4527935488 in file log0log.cc line 308
  InnoDB: Assertion failure in thread 4523442176 in file log0log.cc line 308
  InnoDB: Assertion failure in thread 4522070016 in file log0log.cc line 308
  InnoDB: Assertion failure in thread 4513124352 in file log0log.cc line 308
  InnoDB: Assertion failure in thread 4513398784 in file log0log.cc line 308
  InnoDB: Assertion failure in thread 4520423424 in file log0log.cc line 308
  InnoDB: Assertion failure in thread 4513947648 in file log0log.cc line 308
  InnoDB: Assertion failure in thread 4523716608 in file log0log.cc line 308
  InnoDB: Assertion failure in thread 4518227968 in file log0log.cc line 308
InnoDB: Failing assertion: ++count < 50
InnoDB: Failing assertion: ++count < 50
InnoDB: Failing assertion: ++count < 50
InnoDB: Failing assertion: ++count < 50
InnoDB: Failing assertion: ++count < 50
InnoDB: Failing assertion: ++count < 50
InnoDB: Failing assertion: ++count < 50
InnoDB: Failing assertion: ++count < 50
InnoDB: Failing assertion: ++count < 50
InnoDB: Failing assertion: ++count < 50
InnoDB: Failing assertion: ++count < 50
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.
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.
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.
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.
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.