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 |
[27 Mar 2017 20:26]
Jonathan Shyman
[27 Mar 2017 20:26]
Jonathan Shyman
macOS crash details
Attachment: CrashDump.txt (text/plain), 581.13 KiB.
[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.
[31 Mar 2017 11:50]
Jonathan Shyman
It just happened again. I've also spoken to my coworkers and they are experiencing the same issue. I've attached a spindump and sample from the process while Workbench was hung.
[27 Jul 2017 0:49]
MySQL Verification Team
Thank you for the bug report. I couldn't repeat on MAC Sierra 1012.6, is your result data set bigger?. Thanks.
[27 Jul 2017 12:15]
Jonathan Shyman
It still happens on occasion but I cannot give you an exact set of circumstances which lead to it. It does seem to be less frequent on 10.12.5 than is was on 10.12.3.
[5 Sep 2017 0:16]
MySQL Verification Team
I couldn't repeat the issue, please re-open this bug report if you could provide a repeatable test case. Thanks.