Misleading memory usage information printed in crash situation when Thread Pool used

[Przemek]

MySQL prints this kind of message by each crash stack trace.
By default, the "possible" calculation is made based on max_connections and some session buffers.
But in case the Thread Pool is enabled, instead of max_connections, the thread_pool_max_threads is taken into consideration, which by default is as high as 100K. So we end up with this kind of message:

key_buffer_size=16777216
read_buffer_size=1048576
max_used_connections=45
max_threads=100001
thread_count=59
connection_count=41
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 307677966 K bytes of memory

Even though max_connections may be as low as 150 for example.
As single connection can use only one thread anyway, I think this is misleading, and should be changed so that only smaller out of these two should be taken to this calculation.

[Shahriyar Rzayev (rzayev-sehriyar)]

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-3706