MySQL Bugs: #55388: MySQL Server crashes cause InnoDB database corruption

Bug #55388	MySQL Server crashes cause InnoDB database corruption
Submitted:	20 Jul 2010 8:21	Modified:	23 Aug 2010 14:01
Reporter:	Anton Chernomazov	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Server: Windows	Severity:	S2 (Serious)
Version:	5.1.48	OS:	Windows (Server 2008 SP2 Core)
Assigned to:		CPU Architecture:	Any

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

Error log with backtrace

Attachment: mysql.err (application/octet-stream, text), 13.90 KiB.

my.ini file

Attachment: my.ini (application/octet-stream, text), 8.91 KiB.

When i try to delete all tables from `kav` database, server crashes with following messages.

Attachment: mysql.err (application/octet-stream, text), 5.49 KiB.