InnoDB crash with 5.6.37-82.2

[Thomas Deutschmann]

Maybe this is related to https://bugs.launchpad.net/percona-server/+bug/1736028 (same build environment).

But we now see this in production, i.e. not just in test suite:

A real percona-server crashes after a view minutes with

2017-12-04 14:47:24 6962 [Warning] The option innodb (skip-innodb) is deprecated and will be removed in a future release
2017-12-04 14:47:24 6962 [Note] InnoDB: Using atomics to ref count buffer pool pages
2017-12-04 14:47:24 6962 [Note] InnoDB: The InnoDB memory heap is disabled
2017-12-04 14:47:24 6962 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2017-12-04 14:47:24 6962 [Note] InnoDB: Memory barrier is not used
2017-12-04 14:47:24 6962 [Note] InnoDB: Compressed tables use zlib 1.2.11
2017-12-04 14:47:24 6962 [Note] InnoDB: Using Linux native AIO
2017-12-04 14:47:24 6962 [Note] InnoDB: Using CPU crc32 instructions
2017-12-04 14:47:24 6962 [Note] InnoDB: Initializing buffer pool, size = 1.0G
2017-12-04 14:47:24 6962 [Note] InnoDB: Completed initialization of buffer pool
2017-12-04 14:47:24 6962 [Note] InnoDB: Highest supported file format is Barracuda.
2017-12-04 14:47:24 6962 [Note] InnoDB: 128 rollback segment(s) are active.
2017-12-04 14:47:24 6962 [Note] InnoDB: Waiting for purge to start
2017-12-04 14:47:24 6962 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.37-82.2 started; log sequence number 120332257700
2017-12-04 14:47:24 6962 [Note] RSA private key file not found: /srv/mysql/data//private_key.pem. Some authentication plugins will not work.
2017-12-04 14:47:24 6962 [Note] RSA public key file not found: /srv/mysql/data//public_key.pem. Some authentication plugins will not work.
2017-12-04 14:47:24 6962 [Note] Server hostname (bind-address): '*'; port: 3306
2017-12-04 14:47:24 6962 [Note] IPv6 is available.
2017-12-04 14:47:24 6962 [Note] - '::' resolves to '::';
2017-12-04 14:47:24 6962 [Note] Server socket created on IP: '::'.
2017-12-04 14:47:24 6962 [Warning] 'user' entry 'root@mysql-3' ignored in --skip-name-resolve mode.
2017-12-04 14:47:24 6962 [Warning] 'user' entry '@mysql-3' ignored in --skip-name-resolve mode.
2017-12-04 14:47:24 6962 [Warning] 'proxies_priv' entry '@ root@mysql-3' ignored in --skip-name-resolve mode.
2017-12-04 14:47:24 6962 [Note] Event Scheduler: Loaded 0 events
2017-12-04 14:47:24 6962 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.6.37-82.2-log' socket: '/run/mysqld/mysqld.sock' port: 3306 Source distribution
13:47:35 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.
We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed,
something is definitely wrong and this may fail.
Please help us make Percona Server better by reporting any
bugs at http://bugs.percona.com/

key_buffer_size=5368709120
read_buffer_size=131072
max_used_connections=25
max_threads=152
thread_count=12
connection_count=12
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 5303340 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x7fe4244df000
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 = 7fe449f80690 thread_stack 0x40000
/usr/sbin/mysqld(my_print_stacktrace+0x36)[0x5575684c5d46]
/usr/sbin/mysqld(handle_fatal_signal+0x3d0)[0x557568271200]
/lib64/libpthread.so.0(+0x140f0)[0x7fe4487430f0]
/usr/sbin/mysqld(+0x7b79de)[0x5575685dc9de]
/usr/sbin/mysqld(+0x7ab702)[0x5575685d0702]
/usr/sbin/mysqld(+0x7b0484)[0x5575685d5484]
/usr/sbin/mysqld(+0x7b81dd)[0x5575685dd1dd]
/usr/sbin/mysqld(+0x748599)[0x55756856d599]
/usr/sbin/mysqld(+0x74afd7)[0x55756856ffd7]
/usr/sbin/mysqld(+0x74b5f2)[0x5575685705f2]
/usr/sbin/mysqld(+0x757120)[0x55756857c120]
/usr/sbin/mysqld(+0x6d1f34)[0x5575684f6f34]
/usr/sbin/mysqld(_ZN7handler12ha_write_rowEPh+0x9f)[0x5575681cfc8f]
/usr/sbin/mysqld(_Z12write_recordP3THDP5TABLEP9COPY_INFOS4_+0x99)[0x5575682d24d9]
/usr/sbin/mysqld(_Z12mysql_insertP3THDP10TABLE_LISTR4ListI4ItemERS3_IS5_ES6_S6_15enum_duplicatesb+0xc21)[0x5575682d95f1]
/usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x431c)[0x5575682ec6dc]
/usr/sbin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x4e0)[0x5575682efb30]
/usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x1213)[0x5575682f1473]
/usr/sbin/mysqld(_Z24do_handle_one_connectionP3THD+0x1bd)[0x5575682bff8d]
/usr/sbin/mysqld(handle_one_connection+0x38)[0x5575682c0038]
/usr/sbin/mysqld(pfs_spawn_thread+0xee)[0x5575686e128e]
/lib64/libpthread.so.0(+0x78ea)[0x7fe4487368ea]
/lib64/libc.so.6(clone+0x3f)[0x7fe447b0525f]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (7fe24e1ef010): is an invalid pointer
Connection ID (thread ID): 67
Status: NOT_KILLED

[Shahriyar Rzayev (rzayev-sehriyar)]

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-3762