Bug #86082 | memory leak? in mysql causes system to max ram and swap out | ||
---|---|---|---|
Submitted: | 26 Apr 2017 3:44 | Modified: | 26 May 2017 16:05 |
Reporter: | mike coutinho | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | MySQL Server | Severity: | S1 (Critical) |
Version: | 5.7.18 | OS: | Red Hat |
Assigned to: | CPU Architecture: | Any |
[26 Apr 2017 3:44]
mike coutinho
[26 Apr 2017 16:05]
MySQL Verification Team
Hi! Thank you for your bug report. Please, do know that we can accept only those bugs that are verifiable. This means that a reporter has to provide the analysis of the code which demonstrates the leak or the test case in SQL that demonstrate that memory is not released to the GNU malloc, which is mostly used on Red Hat systems. For the start , you can analyze the configuration of your server and calculate the potential memory that could be allocated for the maximum number of threads that you have observed.
[27 May 2017 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".