MySQL Bugs: #84781: MySQL crash (probably bug)

Bug #84781	MySQL crash (probably bug)
Submitted:	1 Feb 2017 23:35	Modified:	13 Mar 2017 15:56
Reporter:	Michał Korowski	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Server	Severity:	S2 (Serious)
Version:	5.7.17	OS:	FreeBSD
Assigned to:		CPU Architecture:	Any
Tags:	crash

Description:
We have four identical configurations of MySQL. Every few hours MySQL crash.

How to repeat:
Example error log:

17:01:41 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=181
max_threads=1500
thread_count=68
connection_count=67
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 603703 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x18a7092000
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 = 7fffd77bcf48 thread_stack 0x40000
0xfea1b7 <my_print_stacktrace+0x27> at /usr/local/libexec/mysqld
0x7c30a1 <handle_fatal_signal+0x2b1> at /usr/local/libexec/mysqld
0x803800b4a <pthread_sigmask+0x51a> at /lib/libthr.so.3
0x80380022c <pthread_getspecific+0xe1c> at /lib/libthr.so.3

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (18a7087030): insert into ps_product_lang 
                    (id_product, id_shop, id_lang, `name`, description, description_short, available_now, link_rewrite) 
                    values (36,1,1,'...','...','','','')
Connection ID (thread ID): 727364
Status: NOT_KILLED

Hi!

Thank you for your bug report. However, you have provided us with very few data that would enable us to conclude what is the cause of the crash.

First of all, do you use our binaries, that we are building for FreeBSD. If not, then I would recommend that you switch to those. Next, send us your entire set of configurational variables, best by sending configuration files that you use.

Next, send us data on the machines that MySQL runs. Let us know how much RAM they have, is it ECC RAM, how much RAM have you allocated to MySQL and similar. Also, send us free space on each device that hosts MySQL files.

Also, we would suggest that you run our debug binaries on one of the system that crashes most and then send us the entire output.

Last, but not least, if you run that INSERT statement, do you get crash all of the times ??? If you do not get crash, do not forget to DELETE the inserted row.

Thanks in advance.

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".