MySQL Bugs: #92731: Clean up crash message

Bug #92731	Clean up crash message
Submitted:	10 Oct 2018 10:07	Modified:	10 Oct 2018 22:30
Reporter:	Steinar Gunderson	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server: Errors	Severity:	S3 (Non-critical)
Version:	8.0.15	OS:	Any
Assigned to:		CPU Architecture:	Any

Description:
When we hit a fatal signal (e.g. a crash or an assertion error), we print out a lot of information that seems to mostly assume that the error is due to out-of-memory. We then print out

  It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = %lu K  bytes of memory

which hasn't been a reasonable bound for a very long time.

We should just remove this, and in general make the error message shorter and easier to understand.

How to repeat:
N/A

Suggested fix:
N/A

Filed it a decade ago!
https://bugs.mysql.com/bug.php?id=35661
(legacy and incorrect memory formula and message written to error log after crash)

Posted by developer:
 
Fixed in 8.0.15.

The message displayed by mysqld when a fatal signal occurred has been
simplified and made more informative. It also does not display the
calculation of memory usage, which had become out of date and
inaccurate.

Fixed wrong category.