Bug #90988 show engine status or select from INNODB_LOCKS cause crash
Submitted: 23 May 2018 11:37 Modified: 23 May 2018 11:52
Reporter: yx jiang Email Updates:
Status: Can't repeat Impact on me:
Category:MySQL Server Severity:S1 (Critical)
Version:5.6.21 OS:CentOS (6.4)
Assigned to: CPU Architecture:Any
Tags: show engine status

[23 May 2018 11:37] yx jiang
It is very likely with this bug https://bugs.mysql.com/bug.php?id=38883.

And it is said fixed in  5.1.31 as in this document  https://docs.oracle.com/cd/E17952_01/mysql-5.1-relnotes-en/news-5-1-31.html.

But things happenned agaim in 5.6.21. And I haven't found fixing record in 5.6.x release note.

Does this fix lost in 5.6.x

crash info in error log
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 10956785 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x6db9d700
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 = 7fdd8c5f0e18 thread_stack 0x40000

How to repeat:
No repliable way to reproduce.

Suggested fix:
[23 May 2018 11:52] 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 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".  Again, thank you for your
continued support of MySQL.