MySQL Bugs: #46175: NULL read_view and consistent read assertion

Bug #46175	NULL read_view and consistent read assertion
Submitted:	14 Jul 2009 15:33	Modified:	20 Jun 2010 22:29
Reporter:	Adam Erickson	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server: Optimizer	Severity:	S1 (Critical)
Version:	5.1.35, 5.1.39, 5.1.40, 5.1.41,5.4.3	OS:	Any
Assigned to:	Georgi Kodinov	CPU Architecture:	Any
Tags:	assert, crash, innodb, mysqld, segfault, txisolation

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

trx->active_trans == 0, but trx->conc_state != TRX_NOT_STARTED is repeatable, but not the crash :(

Attachment: sbester_tests_5.4.3_windows.txt (text/plain), 11.44 KiB.

gdb output

Attachment: gdb_out.txt (text/plain), 11.01 KiB.

testcase of the reporter

Attachment: bug46175.c (text/x-csrc), 7.74 KiB.

some gdb details from a crash i just got with the above testcase.

Attachment: bug46175_my_gdb_output.txt (text/plain), 81.94 KiB.