5.7 with generated columns crashes with signal 11 Item_func4walkE in backtrace
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
MySQL Server |
Unknown
|
Unknown
|
||||
Percona Server moved to https://jira.percona.com/projects/PS | Status tracked in 5.7 | |||||
5.5 |
Invalid
|
Undecided
|
Unassigned | |||
5.6 |
Invalid
|
Undecided
|
Unassigned | |||
5.7 |
Fix Released
|
High
|
Vlad Lesin |
Bug Description
Server version: 5.7.15-9-log Percona Server (GPL), Release '9', Revision '9f0fd0a'
uname -a
Linux devmysql-dba-vx-2 3.16.0-4-amd64 #1 SMP Debian 3.16.7-
error log:
11:28:47 UTC - mysqld got signal 11 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
Attempting to collect some information that could help diagnose the problem.
As this is a crash and something is definitely wrong, the information
collection process might fail.
Please help us make Percona Server better by reporting any
bugs at http://
key_buffer_
read_buffer_
max_used_
max_threads=201
thread_count=2
connection_count=1
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x7fc0d00749e0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 7fc08a30ce80 thread_stack 0x40000
/usr/sbin/
/usr/sbin/
/lib/x86_
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/lib/x86_
/lib/x86_
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (7fc0d0079690): SHOW TABLE STATUS FROM `testdb` LIKE 'testtbl'
Connection ID (thread ID): 204
Status: NOT_KILLED
You may download the Percona Server operations manual by visiting
http://
in the manual which will help you identify the cause of the crash.
Writing a core file
Segmentation fault (core dumped)
How to reproduce:
1. Create table with following definition (backup of database and table is in archive in attachment):
CREATE TABLE `testtbl` (
`ID` int(11) NOT NULL AUTO_INCREMENT,
`GUID` binary(16) NOT NULL,
`GUIDString` varchar(36) GENERATED ALWAYS AS (lower(
PRIMARY KEY (`ID`),
KEY `IX_testtbl_guid` (`GUID`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8 ROW_FORMAT=DYNAMIC
Where GuidString converts binary GUID field into text form.
2. Run concurrent workload (i've use python script mysql.py, which is in archive in attachment)
3. Connect with mysql CLI and run select from Information_schema or from this table.
4. Percona Server will crash with signal 11
Changed in percona-server: | |
status: | Incomplete → New |
summary: |
- percona server 5.7 crashes with signal 11 Item_func4walkE in backtrace + 5.7 with generated columns crashes with signal 11 Item_func4walkE in + backtrace |
I can't reproduce this, would you be able to share your my.cnf file please.