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: | |
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 |
[23 Mar 2013 0:33]
Karl Nicoletti
[25 Mar 2013 19:36]
Karl Nicoletti
Screen shot of the Win7 resource monitor following DBDoc generation.
Attachment: PostReportGeneration.doc (application/msword, text), 91.50 KiB.
[27 Mar 2013 17:41]
MySQL Verification Team
memory message
Attachment: wb_memory.png (image/png, text), 47.75 KiB.
[27 Mar 2013 17:42]
MySQL Verification Team
Thank you for the bug report. Verified as described.
[28 Jun 2013 0:11]
Philip Olson
Fixed as of the upcoming MySQL Workbench 6.0.3 release, and here's the changelog entry: Executing "Model", "DBDoc", "Model Reporting" created a memory link. Then after the report was generated, executing "File", "Export", "Export as PNG" would fail and report that MySQL Workbench ran out of memory. Thank you for the bug report.