Bug #6563 Log report says assertion failure in ha_innodb.cpp line 4581
Submitted: 10 Nov 2004 22:45 Modified: 11 Nov 2004 20:40
Reporter: Rob Vatz Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Server: InnoDB storage engine Severity:S3 (Non-critical)
Version:4.0.21-debug OS:Windows (Windows XP (with Service Pack 2))
Assigned to: CPU Architecture:Any

[10 Nov 2004 22:45] Rob Vatz
Description:
Started mysqldump and noticed it was taking a long time to run. Then noticed that clients would 
freeze after entering any SELECT statement (nothing returned, no messages)

Error log contained the following:

InnoDB: Error: select_lock_type is 99999999 inside ::start_stmt()
041110 16:03:52InnoDB: Assertion failure in thread 2332 in file C:
\cygwin\home\mysqldev\build\mysql-4.0.21-build....sql\ha_innodb.cpp line 4581
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to bugs.mysql.com

After rebooting entire machine, SELECT work fine.

How to repeat:
I guess run mysqldump on ALL tables in a single database...but I've done that before with no 
problems.
[10 Nov 2004 22:49] Rob Vatz
fixed synopsis text to be more specific
[11 Nov 2004 3:29] MySQL Verification Team
Could you please provide more details about the database schema,
running against previous InnoDB database I have I wasn't able to
repeat.

Thanks
[11 Nov 2004 13:56] Rob Vatz
As requested, I added a file that contains the CREATE TABLE commands used to create the database.
[11 Nov 2004 13:57] Rob Vatz
I forgot to mention....when mass-loading records, I temporarily disable foreign key checking (especially on the patent table), then reactivate it when done.
[11 Nov 2004 20:40] Heikki Tuuri
Hi!

This is the unfortunate

mysqldump --opt

crash that is fixed in 4.0.22. Please upgrade.

Regards,

Heikki