MySQL Bugs: #68755: DBDoc - Model Reporting has GIANT memory leak that eventually crashes MWB

Bug #68755	DBDoc - Model Reporting has GIANT memory leak that eventually crashes MWB
Submitted:	23 Mar 2013 0:33	Modified:	28 Jun 2013 0:11
Reporter:	Karl Nicoletti	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Workbench	Severity:	S3 (Non-critical)
Version:	5.2.46 SE	OS:	Windows (Windows 7 Pro 64Bit SP 1)
Assigned to:		CPU Architecture:	Any
Tags:	crash, memory leaks, model reporting

File:	Maximum allowed size is 50MB.
Description:
Privacy:

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

Screen shot of the Win7 resource monitor following DBDoc generation.

Attachment: PostReportGeneration.doc (application/msword, text), 91.50 KiB.

memory message

Attachment: wb_memory.png (image/png, text), 47.75 KiB.