Bug #93181 mysql crash
Submitted: 14 Nov 2018 0:31 Modified: 14 Nov 2018 7:13
Reporter: Kevin KAN Email Updates:
Status: Can't repeat Impact on me:
None 
Category:MySQL Server Severity:S3 (Non-critical)
Version:5.7.20 OS:CentOS
Assigned to: CPU Architecture:Any

[14 Nov 2018 0:31] Kevin KAN
Description:
2018-11-01T15:06:01.598259Z 1654527 [Warning] IP address '192.168.61.22' could not be resolved: Temporary failure in name resolution
terminate called after throwing an instance of 'std::bad_alloc'
  what():  std::bad_alloc
15:06: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=8388608
read_buffer_size=131072
max_used_connections=293
max_threads=2000
thread_count=193
connection_count=190
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 802910 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x7f25480008c0
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...
2018-11-01T15:06:02.848556Z 1654528 [Warning] IP address '192.168.61.22' could not be resolved: Temporary failure in name resolution
2018-11-01T15:06:02.848639Z 1654529 [Warning] IP address '192.168.61.22' could not be resolved: Temporary failure in name resolution
2018-11-01T15:06:02.848725Z 1654530 [Warning] IP address '192.168.61.22' could not be resolved: Temporary failure in name resolution
stack_bottom = 7f2c31578ea8 thread_stack 0x40000
/usr/local/mysql/bin/mysqld(my_print_stacktrace+0x35)[0xf468f5]
/usr/local/mysql/bin/mysqld(handle_fatal_signal+0x4a4)[0x7cd434]
/lib64/libpthread.so.0(+0xf100)[0x7f3c5d053100]
/lib64/libc.so.6(gsignal+0x37)[0x7f3c5ba475f7]
/lib64/libc.so.6(abort+0x148)[0x7f3c5ba48ce8]
/lib64/libstdc++.so.6(_ZN9__gnu_cxx27__verbose_terminate_handlerEv+0x165)[0x7f3c5c34b9d5]
/lib64/libstdc++.so.6(+0x5e946)[0x7f3c5c349946]
/lib64/libstdc++.so.6(+0x5e973)[0x7f3c5c349973]
/lib64/libstdc++.so.6(+0x5eb93)[0x7f3c5c349b93]
/lib64/libstdc++.so.6(_Znwm+0x7d)[0x7f3c5c34a12d]
/usr/local/mysql/bin/mysqld(_ZNSt6vectorIhSaIhEE15_M_range_insertIPhEEvN9__gnu_cxx17__normal_iteratorIS3_S1_EET_S7_St20forward_iterator_tag+0x1d1)[0xf59521]
/usr/local/mysql/lib/plugin/group_replication.so(_ZN19Transaction_Message12append_cacheEP11st_io_cache+0x65)[0x7f2c8dbb6ff5]
/usr/local/mysql/lib/plugin/group_replication.so(_Z37group_replication_trans_before_commitP11Trans_param+0x8ad)[0x7f2c8dbb7ddd]
/usr/local/mysql/bin/mysqld(_ZN14Trans_delegate13before_commitEP3THDbP11st_io_cacheS3_y+0x1ac)[0xc8079c]
/usr/local/mysql/bin/mysqld(_ZN13MYSQL_BIN_LOG6commitEP3THDb+0x30c)[0xeedc6c]
/usr/local/mysql/bin/mysqld(_Z15ha_commit_transP3THDbb+0x174)[0x81e494]
/usr/local/mysql/bin/mysqld(_Z17trans_commit_stmtP3THD+0x32)[0xdce032]
/usr/local/mysql/bin/mysqld(_Z21mysql_execute_commandP3THDb+0x707)[0xd134e7]
/usr/local/mysql/bin/mysqld(_Z11mysql_parseP3THDP12Parser_state+0x3a5)[0xd18205]
/usr/local/mysql/bin/mysqld(_Z16dispatch_commandP3THDPK8COM_DATA19enum_server_command+0x11bf)[0xd1942f]
/usr/local/mysql/bin/mysqld(_Z10do_commandP3THD+0x194)[0xd1a2f4]
/usr/local/mysql/bin/mysqld(handle_connection+0x29c)[0xdea45c]
/usr/local/mysql/bin/mysqld(pfs_spawn_thread+0x174)[0xf6cba4]
/lib64/libpthread.so.0(+0x7dc5)[0x7f3c5d04bdc5]
/lib64/libc.so.6(clone+0x6d)[0x7f3c5bb0821d]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (7f254800f700): is an invalid pointer
Connection ID (thread ID): 1652930
Status: NOT_KILLED
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:
can not repeat
[14 Nov 2018 7:13] 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 (5.7.24) 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.