MySQL Bugs: #38816: kill + flush tables with read lock + stored procedures causes crashes!

Bug #38816	kill + flush tables with read lock + stored procedures causes crashes!
Submitted:	15 Aug 2008 7:42	Modified:	7 Aug 2009 0:35
Reporter:	Shane Bester (Platinum Quality Contributor)	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server: Stored Routines	Severity:	S1 (Critical)
Version:	5.0.66a, 5.1.22, 5.1.28, 6.0.7	OS:	Any
Assigned to:	Gleb Shchepa	CPU Architecture:	Any
Tags:	flush tables with read lock, KILL

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:

On *nix platforms use the split command e.g. split -b 50MB <my_large_archive> <my_split_archive_prefix>
On windows use WinZip or a similar utility to split the large file

full stack trace and valgrind output

Attachment: bug38816_more_info.txt (text/plain), 68.31 KiB.

testcase. run against server and wait for crash, or check valgrind errors!

Attachment: bug38816.c (text/plain), 7.77 KiB.