Bug #73330 | Workbench crashes trying to open the data model functionality | ||
---|---|---|---|
Submitted: | 18 Jul 2014 17:16 | Modified: | 8 Oct 2014 12:40 |
Reporter: | Stephen Rothman | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | MySQL Workbench: Modeling | Severity: | S2 (Serious) |
Version: | Workbench 6.1.7 | OS: | Windows (Win 7 Pro 64bit) |
Assigned to: | CPU Architecture: | Any |
[18 Jul 2014 17:16]
Stephen Rothman
[21 Aug 2014 15:05]
Alfredo Kojima
Can you paste the output of Help -> System Info?
[21 Aug 2014 21:41]
Stephen Rothman
MySQL Workbench Community (GPL) for Windows version 6.1.7 revision 11891 build 1788 Configuration Directory: C:\Users\srothman.domain\AppData\Roaming\MySQL\Workbench Data Directory: C:\Apps\MySQL\MySQL Workbench CE 6.1.7 Cairo Version: 1.8.8 OS: Microsoft Windows 7 Service Pack 1 (build 7601), 64-bit CPU: 8x Intel(R) Core(TM) i7-4800MQ CPU @ 2.70GHz, 15.9 GiB RAM Active video adapter Intel(R) HD Graphics 4600 Installed video RAM: -1984 MB Current video mode: 1600 x 900 x 4294967296 colors Used bit depth: 32 Driver version: 10.18.10.3412 Installed display drivers: igdumdim64.dll,igd10iumd64.dll,igd10iumd64.dll,igdumdim32,igd10iumd32,igd10iumd32 Current user language: English (United States)
[21 Aug 2014 21:51]
Stephen Rothman
System Properties -> Performance
Attachment: system_props_preformance.png (image/png, text), 83.14 KiB.
[21 Aug 2014 21:58]
Stephen Rothman
I always run windows set to "Adjust for best performance" in the System Properties -> Performance window. I recently switched it to "Adjust for best appearance" and Workbench no longer crashes when I try to access the data modeler. Switching back to "Adjust for best performance" will continuously crash Workbench when I try to access the data modeler.
[8 Sep 2014 12:40]
MySQL Verification Team
I could not repeat even changing Windows Adjust for best performance. Please try Development Releases 6.2.2 rc version. Thanks.
[9 Oct 2014 1:00]
Bugs System
No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open".