| Bug #80727 | Bug: MySqlCommand did not release resources and potential cause memory exhausted | ||
|---|---|---|---|
| Submitted: | 14 Mar 2016 13:18 | Modified: | 22 Mar 2016 14:29 |
| Reporter: | jun wang | Email Updates: | |
| Status: | Verified | Impact on me: | |
| Category: | Connector / NET | Severity: | S2 (Serious) |
| Version: | 6.9 | OS: | Windows (Windows 7) |
| Assigned to: | 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
[14 Mar 2016 13:20]
jun wang
[14 Mar 2016 13:20]
jun wang
Memory Profile screen 2
Attachment: Bug20160314_02.png (image/png, text), 78.22 KiB.
[15 Mar 2016 7:44]
Chiranjeevi Battula
Screenshot.
Attachment: 80727.PNG (image/png, text), 114.17 KiB.
[21 Mar 2016 13:16]
jun wang
test project
Attachment: TestMemory.rar (application/octet-stream, text), 30.71 KiB.
[21 Mar 2016 13:25]
jun wang
When run test memory project, it show mysql object normal
Attachment: Bug20160321_01_TestMemory.png (image/png, text), 150.46 KiB.
[21 Mar 2016 13:26]
jun wang
when run test mem project, it show mysql object abnormal and instance increased continually
Attachment: Bug20160321_02_TestMem.png (image/png, text), 137.61 KiB.
[22 Mar 2016 6:40]
Chiranjeevi Battula
Screenshot.
Attachment: 80727_1.png (image/png, text), 175.97 KiB.
[22 Mar 2016 6:40]
Chiranjeevi Battula
Screenshot.
Attachment: 80727_2.png (image/png, text), 158.95 KiB.
