| Bug #27732 | Possible memory leak with index_merge | ||
|---|---|---|---|
| Submitted: | 10 Apr 2007 13:18 | Modified: | 30 Mar 2008 8:34 |
| Reporter: | Brice Figureau | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Server: Optimizer | Severity: | S1 (Critical) |
| Version: | 5.0.56,5.1.22 | OS: | Any (windows, linux) |
| Assigned to: | CPU Architecture: | Any | |
| Tags: | index_merge, memory leak | ||
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 Apr 2007 13:20]
Brice Figureau
[10 Apr 2007 13:21]
Brice Figureau
pmap snapshot taken a few hours after server start
Attachment: mysql_pmap_20070308.txt (text/plain), 30.45 KiB.
[10 Apr 2007 13:22]
Brice Figureau
pmap snapshot taken a few days ago
Attachment: mysql_pmap_20070408.txt (text/plain), 82.39 KiB.
[5 Feb 2008 14:01]
Shane Bester
this is the testcase I wrote. leaks 20kb/s on my machine.
Attachment: bug27732_testcase.sql (application/unknown, text), 5.57 KiB.
