Bug #82737 "SIGKILL myself" for ALTER TABLE DROP COLUMN command

Submitted: 26 Aug 2016 3:53 Modified: 2 Sep 2016 4:29
Reporter: Roel Van de Paar Email Updates:
Status: Verified Impact on me:
None 
Category:MySQL Server: InnoDB storage engine Severity:S2 (Serious)
Version:5.7.13, 5.7.14 OS:Any
Assigned to: CPU Architecture:Any

[26 Aug 2016 3:53] Roel Van de Paar
Description:
mysql> ALTER TABLE t1 DROP COLUMN c1;
ERROR 2013 (HY000): Lost connection to MySQL server during query

2016-08-26T03:36:19.971367Z 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-08-26T03:36:22.249156Z 2 [Note] InnoDB: innodb_change_buffering_debug flush [page id: space=0, page number=314]
SIGKILL myself
<....end of mysqld error log....>

How to repeat:
DROP DATABASE test;CREATE DATABASE test;USE test;
SET @@GLOBAL.innodb_limit_optimistic_insert_debug=19;
CREATE TABLE t1(c1 TIME KEY,c2 LINESTRING,c3 FLOAT UNSIGNED)ENGINE=InnoDB;
SET @@GLOBAL.innodb_change_buffering_debug=12;
ALTER TABLE t1 DROP COLUMN c1;
[26 Aug 2016 3:58] Roel Van de Paar
Requires debug build
[26 Aug 2016 4:00] Roel Van de Paar
Not reproducible on optimized
[26 Aug 2016 8:27] MySQL Verification Team
Hello Roel,

Thank you for the report.
Observed that 5.7.14 debug build is affected.

Thanks,
Umesh
[2 Sep 2016 4:29] Roel Van de Paar
I am seeing the 'SIGKILL myself' a lot. Is there a reason? What is the cause?

Portions of this website are copyright © 2001, 2002 The PHP Group

Page generated in 0.055 sec. using MySQL 8.4.7-u6-cloud

Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.