Bug #82915 SIGKILL myself when using innodb_limit_optimistic_insert_debug=2 and drop table
Submitted: 9 Sep 2016 2:27 Modified: 9 Sep 2016 5:24
Reporter: Roel Van de Paar Email Updates:
Status: Verified Impact on me:
None 
Category:MySQL Server: DML Severity:S3 (Non-critical)
Version:5.7.13, 5.7.15 OS:Any
Assigned to: CPU Architecture:Any

[9 Sep 2016 2:27] Roel Van de Paar 
Description:
2016-09-09T02:08:34.955880Z 0 [Note] /sda/MS240816-mysql-5.7.14-linux-x86_64-debug/bin/mysqld: ready for connections.
Version: '5.7.14-debug-asan'  socket: '/sda/MS240816-mysql-5.7.14-linux-x86_64-debug/socket.sock'  port: 12265  MySQL Community Server (GPL)
2016-09-09T02:08:38.111533Z 2 [Note] InnoDB: innodb_change_buffering_debug flush [page id: space=0, page number=314]
SIGKILL myself

How to repeat:
SET @@GLOBAL.innodb_limit_optimistic_insert_debug=2;
DROP DATABASE test;CREATE DATABASE test;USE test;
SET @start_global_value=@@global.sort_buffer_size;
SET @@global.innodb_change_buffering_debug=@start_global_value;
CREATE TABLE t1(c1 DOUBLE PRECISION,c2 CHAR (1),c3 INT(1),c4 VARCHAR(1) KEY,c5 DOUBLE PRECISION UNIQUE KEY,c6 FIXED(0,0) DEFAULT 3.141592);
DROP TABLE IF EXISTS t1,t2,t3,t4,t5,t6,t7,t8,t9,t10,t11,t12,t13,t14,t15,t16,t17,t18;
SELECT 1;  # May shows server is gone (wait a bit before executing this one)
SELECT 1;  # Shows server is gone (wait a bit before executing this one)
[9 Sep 2016 5:24] MySQL Verification Team 
Hello Roel,

Thank you for the report and test case.
Observed that 5.7.15 ASAN debug build is affected.

Thanks,
Umesh
[9 Sep 2016 5:26] MySQL Verification Team 
5.7.15 asan build test results

Attachment: 82915.results (application/octet-stream, text), 8.33 KiB.