Bug #102774 | A scenario that result in memory leak | ||
---|---|---|---|
Submitted: | 2 Mar 2021 0:37 | Modified: | 6 Mar 2021 7:13 |
Reporter: | Haixing Weng (OCA) | Email Updates: | |
Status: | Verified | Impact on me: | |
Category: | MySQL Server: DML | Severity: | S3 (Non-critical) |
Version: | 5.7.31,8.0.22, 5.7.33 | OS: | Any |
Assigned to: | CPU Architecture: | Any | |
Tags: | memory leak; |
[2 Mar 2021 0:37]
Haixing Weng
[2 Mar 2021 0:39]
Haixing Weng
memory sampling graph
Attachment: sampling.png (image/png, text), 36.09 KiB.
[2 Mar 2021 0:39]
Haixing Weng
memory sampling data
Attachment: 31818.pid.Rss (application/rss+xml, text), 532.00 KiB.
[2 Mar 2021 11:33]
Haixing Weng
Suggest to running loading test in a long time, by using --time=36000(10hours) or 360000(5days), We observed 200MB memory grows, running in serveral hours up to now, and it seems to nerver stop
[3 Mar 2021 4:08]
Haixing Weng
We still observe memory grows even we had started mysqld with jemalloc lib
[6 Mar 2021 7:13]
MySQL Verification Team
Hello Haixing Weng, Thank you for the report and feedback. Observed the issue with 5.7.33 build with provided configuration and sysbench load. regards, Umesh