Bug #97935 | Memory leak in client connection using information_schema | ||
---|---|---|---|
Submitted: | 10 Dec 2019 2:01 | Modified: | 21 Jan 2021 13:09 |
Reporter: | Daniel Nichter (OCA) | Email Updates: | |
Status: | Won't fix | Impact on me: | |
Category: | MySQL Server: Information schema | Severity: | S2 (Serious) |
Version: | 5.7.28 | OS: | Any |
Assigned to: | MySQL Verification Team | CPU Architecture: | x86 |
Tags: | 5.7, client, connect, disconnect, information_schema, massif, memory-leak, valgrind, vio |
If the data you need to attach is more than 50MB, you should create a compressed archive of the data, split it to 50MB chunks, and upload each of them as a separate attachment.
To split a large file:
- On *nix platforms use the split command e.g.
split -b 50MB <my_large_archive> <my_split_archive_prefix>
- On windows use WinZip or a similar utility to split the large file
[10 Dec 2019 13:32]
Daniel Nichter
[10 Dec 2019 13:33]
Daniel Nichter
SHOW GLOBAL VARIABLES
Attachment: global_vars.txt (text/plain), 15.19 KiB.
[13 Dec 2019 20:54]
Daniel Nichter
monitor.sh
Attachment: monitor.sh (text/x-sh), 333 bytes.
[13 Dec 2019 20:55]
Daniel Nichter
Log changes to RSS of given PID
Attachment: record-rss.sh (text/x-sh), 361 bytes.
[13 Dec 2019 20:56]
Daniel Nichter
2h output of record-rss.sh from running monitor.sh
Attachment: 2h-rss-mysqld-direct.csv (text/csv), 14.83 KiB.
[13 Dec 2019 20:58]
Daniel Nichter
Graph of mysqld RSS from running method 2
Attachment: method-2-rss-graph.png (image/png, text), 101.26 KiB.