Bug #80309 some innodb tests fail with address sanitizer (WITH_ASAN)
Submitted: 8 Feb 2016 20:53 Modified: 9 Feb 2016 11:37
Reporter: Richard Prohaska Email Updates:
Status: Verified Impact on me:
Category:MySQL Server: InnoDB storage engine Severity:S3 (Non-critical)
Version:5.7.11 OS:Ubuntu (15.10)
Assigned to: CPU Architecture:Any

[8 Feb 2016 20:53] Richard Prohaska
When mysql is compiled with the address sanitizer ON, the innodb.alter_kill, the innodb.log_file_name, and the innodb.tablespace_crash tests fail due to memory leaks.  InnoDB just exits the process sometimes.  See http://prohaska7.blogspot.com/2015/10/mysql-57-versus-address-sanitizer.html for details.

How to repeat:
mtr innodb.log_file_name

innodb.log_file_name                     [ fail ]
        Test ended at 2016-02-08 15:51:19

CURRENT_TEST: innodb.log_file_name
mysqltest: At line 53: command "$mysqld" failed with wrong error: 1

cat var/log/my_restart.err
2016-02-08T20:51:14.922793Z 0 [ERROR] InnoDB: Tablespace 24 was not found at ./test/t3.ibd.
2016-02-08T20:51:14.922804Z 0 [ERROR] InnoDB: Set innodb_force_recovery=1 to ignore this and to permanently lose all changes to the tablespace.
2016-02-08T20:51:14.922862Z 0 [ERROR] InnoDB: Cannot continue operation.

==27729==ERROR: LeakSanitizer: detected memory leaks

Direct leak of 221040 byte(s) in 1535 object(s) allocated from:
[9 Feb 2016 11:37] MySQL Verification Team
Hello Richard Prohaska,

Thank you for the bug report.