Bug #91719 UTC - mysqld got signal 11 ;
Submitted: 19 Jul 2018 14:30 Modified: 27 Aug 2018 11:53
Reporter: Peter Markov Email Updates:
Status: Can't repeat Impact on me:
None 
Category:MySQL Server: InnoDB storage engine Severity:S2 (Serious)
Version:5.7.22 OS:Debian (Linux server0 4.9.0-6-amd64 #1 SMP Debian 4.9.88-1+deb9u1 (2018-05-07) x86_64 GNU/Linux)
Assigned to: CPU Architecture:Any (Intel® Core™ i7-6700 Quadcore Skylake 64 GB DDR4 2 x 500 GB, SATA 6 Gb/s, SSD)

[19 Jul 2018 14:30] Peter Markov
Description:
07:22:00 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.
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=86
max_threads=800
thread_count=10
connection_count=10
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 326092 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x7f6dd8536150
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-07-18 01:25:06 0x7f8625b6f700  InnoDB: Assertion failure in thread 140214135092992 in file rem0rec.cc line 578
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.
22:25:06 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=160
max_threads=800
thread_count=9
connection_count=9
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 326092 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x7f85dc0b0f00
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 = 7f8625b6ee80 thread_stack 0x40000
/usr/sbin/mysqld(my_print_stacktrace+0x2c)[0x55bd92ca91ec]
/usr/sbin/mysqld(handle_fatal_signal+0x479)[0x55bd925d7e59]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x110c0)[0x7f88cb7690c0]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0xcf)[0x7f88c9ef5fff]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x16a)[0x7f88c9ef742a]
/usr/sbin/mysqld(+0x628387)[0x55bd925ae387]
/usr/sbin/mysqld(_Z20rec_get_offsets_funcPKhPK12dict_index_tPmmPP16mem_block_info_t+0x56)[0x55bd92d99106]
/usr/sbin/mysqld(+0xf1710a)[0x55bd92e9d10a]
/usr/sbin/mysqld(_Z24btr_search_guess_on_hashP12dict_index_tP12btr_search_tPK8dtuple_tmmP9btr_cur_tmP5mtr_t+0x951)[0x55bd92e9fb91]
/usr/sbin/mysqld(_Z27btr_cur_search_to_nth_levelP12dict_index_tmPK8dtuple_t15page_cur_mode_tmP9btr_cur_tmPKcmP5mtr_t+0x3ca)[0x55bd92e93cfa]
/usr/sbin/mysqld(+0xe62429)[0x55bd92de8429]
/usr/sbin/mysqld(_Z15row_search_mvccPh15page_cur_mode_tP14row_prebuilt_tmm+0x1b90)[0x55bd92def1f0]
/usr/sbin/mysqld(_ZN11ha_innobase13general_fetchEPhjj+0x6a)[0x55bd92ce5f9a]
/usr/sbin/mysqld(_ZN7handler18ha_index_next_sameEPhPKhj+0x136)[0x55bd92625a96]
/usr/sbin/mysqld(+0xac20fa)[0x55bd92a480fa]
/usr/sbin/mysqld(_Z10sub_selectP4JOINP7QEP_TABb+0x187)[0x55bd92a4ebe7]
/usr/sbin/mysqld(+0xac35aa)[0x55bd92a495aa]
/usr/sbin/mysqld(_Z10sub_selectP4JOINP7QEP_TABb+0x170)[0x55bd92a4ebd0]
/usr/sbin/mysqld(+0xac35aa)[0x55bd92a495aa]
/usr/sbin/mysqld(_Z10sub_selectP4JOINP7QEP_TABb+0x170)[0x55bd92a4ebd0]
/usr/sbin/mysqld(_ZN4JOIN4execEv+0x370)[0x55bd92a479f0]
/usr/sbin/mysqld(_Z12handle_queryP3THDP3LEXP12Query_resultyy+0x233)[0x55bd92ab6823]
/usr/sbin/mysqld(+0x61be6d)[0x55bd925a1e6d]
/usr/sbin/mysqld(_Z21mysql_execute_commandP3THDb+0x48e7)[0x55bd92a7a4a7]
/usr/sbin/mysqld(_Z11mysql_parseP3THDP12Parser_state+0x395)[0x55bd92a7cab5]
/usr/sbin/mysqld(_Z16dispatch_commandP3THDPK8COM_DATA19enum_server_command+0xfc4)[0x55bd92a7db74]
/usr/sbin/mysqld(_Z10do_commandP3THD+0x197)[0x55bd92a7ef27]
/usr/sbin/mysqld(handle_connection+0x270)[0x55bd92b3a320]
/usr/sbin/mysqld(pfs_spawn_thread+0x1b4)[0x55bd9300f314]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x7494)[0x7f88cb75f494]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x3f)[0x7f88c9fabacf]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (7f85dc3cd2b0): SELECT user.joindate, user.userid, user.membergroupids, user.posts, user.reputation,   user.usergroupid, user.displaygroupid, user.customtitle, user.username, user.ipoints,   userpromotion.joinusergroupid, userpromotion.reputation AS jumpreputation, userpromotion.posts AS jumpposts,   userpromotion.date AS jumpdate, userpromotion.type, userpromotion.strategy,   usergroup.title, usergroup.usertitle AS ug_usertitle,   usertextfield.rank  FROM user AS user  INNER JOIN userpromotion AS userpromotion ON (user.usergroupid = userpromotion.usergroupid)  LEFT JOIN usergroup AS usergroup ON (userpromotion.joinusergroupid = usergroup.usergroupid)  LEFT JOIN usertextfield AS usertextfield ON (usertextfield.userid = user.userid)  WHERE user.lastactivity >= 1531862703
Connection ID (thread ID): 17030599
Status: NOT_KILLED

How to repeat:
every week,  sometimes even more frequently
[24 Jul 2018 12:52] MySQL Verification Team
Hi,

Thank you for your bug report.

In order to be able to verify this bug report, we must be able to reproduce the behaviour ourselves. Hence, we need a test case that will always lead to the stacktrace that you have sent us. Test case is in the form of the set of SQL statements and / or settings that lead always to the stacktrace like the one that you have sent us.

As an example of what the test case looks like, take a look at the short one which was forwarded to us in the following bug report:

https://bugs.mysql.com/bug.php?id=90140

Thanks in advance.
[25 Aug 2018 1:00] Bugs System
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".