Bug #75784 | InnoDB: Failing assertion: level <= 50 in file btr0btr.ic line 126 | ||
---|---|---|---|
Submitted: | 5 Feb 2015 3:45 | Modified: | 5 Feb 2015 21:20 |
Reporter: | Roel Van de Paar | Email Updates: | |
Status: | Can't repeat | Impact on me: | |
Category: | MySQL Server | Severity: | S6 (Debug Builds) |
Version: | 5.7.5-m15 | OS: | Any |
Assigned to: | CPU Architecture: | Any |
[5 Feb 2015 3:45]
Roel Van de Paar
[5 Feb 2015 3:46]
Roel Van de Paar
Though the testcase above should suffice for reproducing the bug, the attached tarball gives the testcase as an exact match of our system, including some handy utilities $ vi {epoch}_mybase # Update base path in this file (the only change required!) $ ./{epoch}_init # Initializes the data dir $ ./{epoch}_start # Starts mysqld $ ./{epoch}_cl # To check mysqld is up $ ./{epoch}_run # Run the testcase (produces output) $ vi /dev/shm/{epoch}/error.log.out # Verify the error log $ ./{epoch}_gdb # Brings you to a gdb prompt attached to correct mysqld & generated core $ ./{epoch}_parse_core # Create {epoch}_STD.gdb and {epoch}_FULL.gdb; standard and full var gdb stack traces etc.
[5 Feb 2015 3:46]
Roel Van de Paar
Scripts, if needed
Attachment: 1423018579_bug_bundle.tar.gz (application/gzip, text), 149.30 KiB.
[5 Feb 2015 3:53]
Roel Van de Paar
See bug 74605 See bug 74577 Hmm, maybe this bug was fixed in 5.7.6 ?
[5 Feb 2015 10:35]
MySQL Verification Team
Not repeatable with 10 days older source. C:\dbs>c:\dbs\5.7\bin\mysql -uroot --port=3570 --prompt="mysql 5.7 > " Welcome to the MySQL monitor. Commands end with ; or \g. Your MySQL connection id is 1 Server version: 5.7.6-m16-debug Source distribution Copyright (c) 2000, 2015, Oracle and/or its affiliates. All rights reserved. Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners. Type 'help;' or '\h' for help. Type '\c' to clear the current input statement. mysql 5.7 > DROP DATABASE test;CREATE DATABASE test;USE test; Query OK, 4 rows affected (1.56 sec) Query OK, 1 row affected (0.00 sec) Database changed mysql 5.7 > SET GLOBAL innodb_file_format=Barracuda; Query OK, 0 rows affected (0.00 sec) mysql 5.7 > set global innodb_large_prefix=-3; Query OK, 0 rows affected (0.00 sec) mysql 5.7 > CREATE TABLE t1(c_1vc VARCHAR (4000),c_2vc VARCHAR (4000),PRIMARY KEY (c_1vc(948))) ROW_FORMAT=COMPRESSED KEY_BLOCK_SIZE=2,engine=innodb; Query OK, 0 rows affected (0.30 sec) mysql 5.7 > INSERT INTO t1 VALUES(REPEAT("a",4000),REPEAT("o",4000)); Query OK, 1 row affected (0.14 sec) mysql 5.7 > SET GLOBAL innodb_limit_optimistic_insert_debug=1; Query OK, 0 rows affected (0.00 sec) mysql 5.7 > UPDATE t1 SET c_1vc=REPEAT("c",4000); Query OK, 1 row affected (0.03 sec) Rows matched: 1 Changed: 1 Warnings: 0 mysql 5.7 >
[5 Feb 2015 10:38]
MySQL Verification Team
Thank you for the bug report. Not repeatable with recent debug build: mysql 5.7 > UPDATE t1 SET c_1vc=REPEAT("c",4000); Query OK, 1 row affected (0.03 sec) Rows matched: 1 Changed: 1 Warnings: 0 mysql 5.7 > show variables like "%version%"; +-------------------------+---------------------+ | Variable_name | Value | +-------------------------+---------------------+ | innodb_version | 5.7.6 | | protocol_version | 10 | | slave_type_conversions | | | version | 5.7.6-m16-debug | | version_comment | Source distribution | | version_compile_machine | x86_64 | | version_compile_os | Win64 | +-------------------------+---------------------+ 7 rows in set (0.00 sec)
[5 Feb 2015 21:20]
Roel Van de Paar
Thanks Miguel, looks like 5.7.6 is all good in this area then.