Bug #48726 mysqld keeps crashing with SIGSEGV with myisam_use_mmap enabled
Submitted: 12 Nov 2009 12:50 Modified: 29 Nov 2011 14:59
Reporter: Dino Tsoumakis Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: General Severity:S1 (Critical)
Version:5.1.40 5.1.43 5.1.48, 5.1.50, 5.1.52-bzr, 5.6.1 OS:Linux (SUSE Linux Enterprise Server 10 (x86_64))
Assigned to: CPU Architecture:Any
Tags: myisam_use_mmap, regression

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

If the data you need to attach is more than 50MB, you should create a compressed archive of the data, split it to 50MB chunks, and upload each of them as a separate attachment.

To split a large file:

[12 Nov 2009 12:53] Dino Tsoumakis
/etc/my.cnf

Attachment: my.cnf (application/octet-stream, text), 2.26 KiB.

[2 Feb 2010 13:37] Dino Tsoumakis
mysqld.log with debuginfos

Attachment: mysqld.log (application/octet-stream, text), 0 bytes.

[2 Feb 2010 13:38] Dino Tsoumakis
mysqld.log with debuginfos

Attachment: mysqld.log (text/x-log), 6.81 KiB.

[29 Sep 2010 8:22] Shane Bester
this reliably crashes my 5.1.50 on fedora core 13. Can somebody test else this please?  import with --force option in client

Attachment: tables.sql (application/octet-stream, text), 38.70 KiB.

[6 Mar 2014 8:24] Abhijit Buchake
my.cnf file

Attachment: bug_my.cnf (application/octet-stream, text), 2.73 KiB.