MySQL Bugs: #75245: Segfault on large row purge in main thread on startup

Bug #75245	Segfault on large row purge in main thread on startup
Submitted:	17 Dec 2014 14:16	Modified:	24 Dec 2014 10:05
Reporter:	Tyler Mitchell	Email Updates:
Status:	Duplicate	Impact on me:	None
Category:	MySQL Server: InnoDB storage engine	Severity:	S1 (Critical)
Version:	5.5.41, 5.6.22, 5.6.23	OS:	Linux (x86_64)
Assigned to:		CPU Architecture:	Any
Tags:	139, ib_warn_row_too_big, innodb, purge

File:	Maximum allowed size is 3MB.
Description:
Privacy:

If the data you need to attach is more than 3MB, you should create a compressed archive of the data and a README file that describes the data with a filename that includes the bug number (recommended filename: mysql-bug-data-75245.zip) and upload one to sftp.oracle.com. A free Oracle Web (SSO) account (the one you use to login bugs.mysql.com) and a client that supports SFTP are required in order to access the SFTP server.

To upload the file to sftp.oracle.com:

Open an SFTP client and connect to sftp.oracle.com. Specify port 2021 and remote directory /support/incoming/.
Log in with your newly created Oracle Web account (email address) and password.
Upload the archive to /support/incoming.
Once you have uploaded the file, add a comment to this bug to notify us about it.

Example: sftp -oPort=2021 -oUser=email sftp.oracle.com:/support/incoming

Usage Notes: This directory is unlistable, which means that once you have uploaded your file, you will not be able to see it. A file cannot be uploaded more than once with the same filename. The filename must be changed before attempting to upload the file again. The filename should always start with mysql-bug- prefix. Files are retained on the SFTP server for 7 days and then permanently removed.

Stack trace

Attachment: bt_ib_warn_row_too_big_segv.txt (text/plain), 5.90 KiB.

my.cnf

Attachment: mycnf_ib_warn_row_too_big_segv.txt (text/plain), 2.25 KiB.