Bug #85660 | MySQL Workbench stops responding, uses all system application memory | ||
---|---|---|---|
Submitted: | 27 Mar 2017 20:26 | Modified: | 5 Sep 2017 0:16 |
Reporter: | Jonathan Shyman | Email Updates: | |
Status: | Can't repeat | Impact on me: | |
Category: | MySQL Workbench | Severity: | S2 (Serious) |
Version: | 6.3.9 | OS: | MacOS (10.12.3) |
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
[27 Mar 2017 20:26]
Jonathan Shyman
[31 Mar 2017 11:49]
Jonathan Shyman
Spindump while Workbench was hung, before crashing
Attachment: Spindump.zip (application/zip, text), 1.12 MiB.
[31 Mar 2017 11:49]
Jonathan Shyman
Sample of Workbench during hang
Attachment: Sample of MySQLWorkbench.zip (application/zip, text), 47.73 KiB.