| Bug #53880 | agent 2.2.1 shows growing Agent Memory Usage (memory leak) on Windows | ||
|---|---|---|---|
| Submitted: | 21 May 2010 12:22 | Modified: | 29 Jun 2010 7:44 |
| Reporter: | Carsten Segieth | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Enterprise Monitor: Agent | Severity: | S1 (Critical) |
| Version: | 2.2.1.1717 | OS: | Windows |
| Assigned to: | Michael Schuster | CPU Architecture: | Any |
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
[21 May 2010 13:03]
Carsten Segieth
[21 May 2010 13:04]
Carsten Segieth
fresh installed 2.2.1.1717 with debug log
Attachment: bug#53880 - agent 2.2.1 mem leak on Win - Win agent started with debug log.jpg (image/jpeg, text), 111.19 KiB.
[28 May 2010 14:46]
Enterprise Tools JIRA Robot
Attachment: 10380_agent-mem.png.jpg (image/jpeg, text), 138.43 KiB.
[17 Jun 2010 5:49]
Carsten Segieth
agent 2.2.2.1726 does not show the mem growth for me
Attachment: bug#53880 - 2.2.2.1726 does not show mem growth for me.jpg (image/jpeg, text), 135.92 KiB.
[18 Jun 2010 6:13]
Carsten Segieth
Build 2.2.2.1726 doesn't show signif. growth after 1.5 days. Jump at 10.00 h caused by network trouble, happened to all agents
Attachment: bug#53880 - 2.2.2.1726 does not show significant mem growth after 1.5 days.jpg (image/jpeg, text), 131.13 KiB.
[18 Jun 2010 6:27]
Carsten Segieth
also on Bill's test system (which is completly separate from my tests) the agent mem looks fine
Attachment: bug#53880 - 2.2.2.1726 does not show significant mem growth after 1.5 days (Bill's testsystem).jpg (image/jpeg, text), 111.65 KiB.
