| Bug #29952 | memory leak error in client library | ||
|---|---|---|---|
| Submitted: | 22 Jul 2007 0:48 | Modified: | 3 Aug 2007 15:26 |
| Reporter: | Shane Bester (Platinum Quality Contributor) | Email Updates: | |
| Status: | Not a Bug | Impact on me: | |
| Category: | MySQL Server: C API (client library) | Severity: | S3 (Non-critical) |
| Version: | 5.0.46 | OS: | Windows |
| Assigned to: | Evgeny Potemkin | CPU Architecture: | Any |
| Tags: | bfsm_2007_08_02 | ||
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
[22 Jul 2007 0:54]
Shane Bester
[1 Aug 2007 15:47]
Shane Bester
testcase, fyi, which doesn't appear to leak memory after fixing it :-/
Attachment: bug29952.c (text/plain), 10.58 KiB.
