MySQL Bugs: #86377: MySQL crashes daily and a restart has to be initiated

Bug #86377	MySQL crashes daily and a restart has to be initiated
Submitted:	18 May 2017 19:50	Modified:	18 May 2017 20:59
Reporter:	Corey Chaltas	Email Updates:
Status:	Can't repeat	Impact on me:	None
Category:	MySQL Server	Severity:	S2 (Serious)
Version:	5.7.12	OS:	Debian
Assigned to:		CPU Architecture:	Any

Description:
Daily/Randomly 2 of my MySQL servers crash with the same errors: 

*** buffer overflow detected ***: /usr/sbin/mysqld terminated
======= Backtrace: =========
/lib/x86_64-linux-gnu/libc.so.6(__fortify_fail+0x37)[0x7ffc4e9d8a97]
/lib/x86_64-linux-gnu/libc.so.6(+0xf1950)[0x7ffc4e9d7950]
/usr/sbin/mysqld(_Z19find_or_create_hostP10PFS_threadPKcj+0x342)[0x10130b2]
/usr/sbin/mysqld(_Z22find_or_create_accountP10PFS_threadPKcjS2_j+0x302)[0x105ab92]
/usr/sbin/mysqld(_Z18set_thread_accountP10PFS_thread+0x3d)[0x1016c1d]
/usr/sbin/mysqld(pfs_set_thread_account_v1+0xad)[0xfff29d]
/usr/sbin/mysqld(_Z16acl_authenticateP3THD19enum_server_command+0xcf7)[0x95c567]
/usr/sbin/mysqld[0xdb8dbd]
/usr/sbin/mysqld(_Z22thd_prepare_connectionP3THD+0x5e)[0xdb9d8e]
/usr/sbin/mysqld(handle_connection+0x243)[0xe9f4e3]
/usr/sbin/mysqld(pfs_spawn_thread+0x1b4)[0xffec74]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x6b50)[0x7ffc5007fb50]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7ffc4e9c430d]
======= Memory map: ========
00400000-01ba4000 r-xp 00000000 08:02 914572                             /usr/sbin/mysqld
01da3000-01e98000 r--p 017a3000 08:02 914572                             /usr/sbin/mysqld
01e98000-01f42000 rw-p 01898000 08:02 914572                             /usr/sbin/mysqld
01f42000-1cacb000 rw-p 00000000 00:00 0                                  [heap]
7ffa70000000-7ffa71be5000 rw-p 00000000 00:00 0 
7ffa71be5000-7ffa74000000 ---p 00000000 00:00 0 
7ffa7671e000-7ffa7671f000 ---p 00000000 00:00 0 
7ffa7671f000-7ffa7675f000 rw-p 00000000 00:00 0                          [stack:9087]
7ffa7675f000-7ffa76760000 ---p 00000000 00:00 0 
7ffa76760000-7ffa767a0000 rw-p 00000000 00:00 0                          [stack:9086]
7ffa767a0000-7ffa767a1000 ---p 00000000 00:00 0 
7ffa767a1000-7ffa767e1000 rw-p 00000000 00:00 0                          [stack:9085]
7ffa767e1000-7ffa767e2000 ---p 00000000 00:00 0 
7ffa767e2000-7ffa76822000 rw-p 00000000 00:00 0                          [stack:9084]
7ffa76822000-7ffa76823000 ---p 00000000 00:00 0 
7ffa76823000-7ffa76863000 rw-p 00000000 00:00 0                          [stack:9083]
7ffa76863000-7ffa76864000 ---p 00000000 00:00 0 
7ffa76864000-7ffa768a4000 rw-p 00000000 00:00 0                          [stack:9082]
7ffa768a4000-7ffa768a5000 ---p 00000000 00:00 0 
7ffa768a5000-7ffa768e5000 rw-p 00000000 00:00 0                          [stack:9081]
7ffa768e5000-7ffa768e6000 ---p 00000000 00:00 0 
7ffa768e6000-7ffa76926000 rw-p 00000000 00:00 0                          [stack:9080]
7ffa76926000-7ffa76927000 ---p 00000000 00:00 0 
7ffa76927000-7ffa76967000 rw-p 00000000 00:00 0                          [stack:9079]
7ffa76967000-7ffa769

How to repeat:
Unknown

my config file

Attachment: mycnf.txt (text/plain), 1.94 KiB.

Full crash file

Attachment: full crash.txt (text/plain), 52.43 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 -- 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".