Bug #94098 InnoDB: Assertion failure in thread 139641453184768 in file trx0trx.ic line 213
Submitted: 28 Jan 2019 11:35 Modified: 28 Jan 2019 12:21
Reporter: Machiel Richards Email Updates:
Status: Can't repeat Impact on me:
None 
Category:MySQL Server Severity:S1 (Critical)
Version:5.7.13-6-log OS:Ubuntu
Assigned to: CPU Architecture:x86
Tags: assertion failure

[28 Jan 2019 11:35] Machiel Richards
Description:
Server has been crashing at least every few days with the following error : 

InnoDB: Assertion failure in thread 139641453184768 in file trx0trx.ic line 213

InnoDB: Failing assertion: !trx->has_search_latch
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
11:04:02 UTC - mysqld got signal 6 ;
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.

key_buffer_size=67108864
read_buffer_size=262144
max_used_connections=42
max_threads=301
thread_count=56
connection_count=20
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 223359 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x7f00e0864000
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 = 7f00cf367e00 thread_stack 0x80000
/usr/sbin/mysqld(my_print_stacktrace+0x2c)[0xec564c]
/usr/sbin/mysqld(handle_fatal_signal+0x461)[0x79cbc1]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x10330)[0x7f2cdfee9330]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x37)[0x7f2cdf32ac37]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x148)[0x7f2cdf32e028]
/usr/sbin/mysqld[0x76b718]
/usr/sbin/mysqld[0x760f54]
/usr/sbin/mysqld[0xef8f75]
/usr/sbin/mysqld(_Z18close_thread_tableP3THDPP5TABLE+0x27a)[0xc472aa]
/usr/sbin/mysqld(_Z19close_thread_tablesP3THD+0x33b)[0xc4794b]
/usr/sbin/mysqld[0xd03a6b]
/usr/sbin/mysqld(_Z14get_all_tablesP3THDP10TABLE_LISTP4Item+0x6e2)[0xd04282]
/usr/sbin/mysqld[0xced60c]
/usr/sbin/mysqld(_Z24get_schema_tables_resultP4JOIN23enum_schema_table_state+0x1cf)[0xd001ff]
/usr/sbin/mysqld(_ZN4JOIN14prepare_resultEv+0x6d)[0xce348d]
/usr/sbin/mysqld(_ZN4JOIN4execEv+0x80)[0xc749a0]
/usr/sbin/mysqld(_Z12handle_queryP3THDP3LEXP12Query_resultyy+0x17d)[0xce3dbd]
/usr/sbin/mysqld[0x75c21d]
/usr/sbin/mysqld(_Z21mysql_execute_commandP3THDb+0x46ae)[0xca731e]
/usr/sbin/mysqld(_Z11mysql_parseP3THDP12Parser_state+0x5c5)[0xcaa385]
/usr/sbin/mysqld(_Z16dispatch_commandP3THDPK8COM_DATA19enum_server_command+0x92f)[0xcaad3f]
/usr/sbin/mysqld(_Z10do_commandP3THD+0x1b7)[0xcac6d7]
/usr/sbin/mysqld(handle_connection+0x2a8)[0xd6db28]
/usr/sbin/mysqld(pfs_spawn_thread+0x1b4)[0x12312f4]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x8184)[0x7f2cdfee1184]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f2cdf3ee37d]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (7f00e0886030): SELECT table_schema, table_name, column_name, auto_increment,     pow(2, case data_type       when 'tinyint'   then 7       when 'smallint'  then 15       when 'mediumint' then 23       when 'int'       then 31       when 'bigint'    then 63       end+(column_type like '% unsigned'))-1 as max_int     FROM information_schema.tables t     JOIN information_schema.columns c USING (table_schema,table_name)     WHERE c.extra = 'auto_increment' AND t.auto_increment IS NOT NULL
Connection ID (thread ID): 961301
Status: NOT_KILLED

How to repeat:
Not able to repeat manually
[28 Jan 2019 12:21] MySQL Verification Team
Thank you for taking the time to report a problem.  Unfortunately you
are not using a current version of the product you reported a problem
with -- the problem might already be fixed. Please download
a new version from http://www.mysql.com/downloads/.

Also, there is no test case provided in the bug report and hence there
is nothing we can verify here.  If you are able to reproduce the bug
with one of the latest versions, please attach the exact reproducible
test case and change the version on this bug report to the version you
tested.  Again, thank you for your continued support of MySQL.