Bug #90163 crash on lots of inserts
Submitted: 21 Mar 2018 14:56 Modified: 22 Apr 2018 21:53
Reporter: Patrick Oberdorf Email Updates:
Status: No Feedback Impact on me:
Category:MySQL Server Severity:S2 (Serious)
Version:5.7.21 OS:Ubuntu (16.04)
Assigned to: MySQL Verification Team CPU Architecture:x86
Tags: crash

[21 Mar 2018 14:56] Patrick Oberdorf
MySQL Server crashes randomly. Happens after a lot of INSERTS and UPDATES.

How to repeat:
I don't know if it is reproducible, because it happens randomly.
[21 Mar 2018 14:57] Patrick Oberdorf
crash log

Attachment: mysql-stacktrace.txt (text/plain), 2.44 KiB.

[21 Mar 2018 14:58] Patrick Oberdorf
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 76385 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x7f40a407fd80
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 = 7f4100085e70 thread_stack 0x40000

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (7f40a4011cc0): is an invalid pointer
Connection ID (thread ID): 423
[22 Mar 2018 21:53] MySQL Verification Team

There's not enough data in the bug report to let us figure out what might be the problem. The crash is during a join from what I see, so probbly a SELECT but does not have to be. 

Can you get us more stack traces from more crashes (you say you get them randomly)?

Could you copy the datadir to a test machine and do some tests to reproduce on a testing system instead on a production one?

[23 Apr 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".