MySQL Bugs: #91387: mysql crash, Assertion failure in file srv0srv.cc line 1756

Bug #91387	mysql crash, Assertion failure in file srv0srv.cc line 1756
Submitted:	24 Jun 2018 3:29	Modified:	2 Jul 2018 8:53
Reporter:	Kevin Zhang	Email Updates:
Status:	Can't repeat	Impact on me:	None
Category:	MySQL Server: InnoDB storage engine	Severity:	S1 (Critical)
Version:	5.6.30	OS:	CentOS
Assigned to:		CPU Architecture:	x86
Tags:	5.6.30, crash, delete, shutdown, signal 6, srv0srv.cc, truncate, UPDATE

Description:
mysql 5.6.30 crash 

error:
InnoDB: ###### Diagnostic info printed to the standard error stream
InnoDB: Error: semaphore wait has lasted > 600 seconds
InnoDB: We intentionally crash the server, because it appears to be hung.
2018-06-24 05:15:57 7f0acb7fe700  InnoDB: Assertion failure in thread 139684340557568 in file srv0srv.cc line 1756
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.6/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
21:15:58 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.
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.

key_buffer_size=8388608
read_buffer_size=2097152
max_used_connections=127
max_threads=1000
thread_count=20
connection_count=16
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 18452988 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0
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 = 0 thread_stack 0x40000
/usr/sbin/mysqld(my_print_stacktrace+0x3b)[0x8e48eb]
/usr/sbin/mysqld(handle_fatal_signal+0x491)[0x674141]
/lib64/libpthread.so.0(+0xf100)[0x7f1b9cb64100]
/lib64/libc.so.6(gsignal+0x37)[0x7f1b9b75f5f7]
/lib64/libc.so.6(abort+0x148)[0x7f1b9b760ce8]
/usr/sbin/mysqld[0x9cf6a7]
/lib64/libpthread.so.0(+0x7dc5)[0x7f1b9cb5cdc5]
/lib64/libc.so.6(clone+0x6d)[0x7f1b9b820ced]
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.

How to repeat:
unknown

mysql error log

Attachment: error.log (application/octet-stream, text), 504.52 KiB.

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 (current release 5.6.40)-- 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 and change the status back to "Open".  Again, thank you for your
continued support of MySQL.

cron sql script

Attachment: cron.sql (application/octet-stream, text), 2.73 KiB.

mysql conf file

Attachment: my.cnf (application/octet-stream, text), 1.96 KiB.

reopen

reopen

when execute long truncate table and insert into

Thank you for your feedback but I'm fully agree with what our Miguel wrote in his previous note. Please note that we don't fix bugs in old versions, don't backport bug fixes, so you have to check with latest version anyway. So, please, upgrade and inform us if problem still exists. Also, we need exact reproducible test case including exact schema, subset of data which required to trigger the reported issue and not just the queries.

If you are able to reproduce the bug with one of the latest versions, please change the version on this bug report to the version you tested and change the status back to "Open".  Again, thank you for your continued support of MySQL.