Bug #55086 | Double-click Workbench File locks up PC indefinitely | ||
---|---|---|---|
Submitted: | 8 Jul 2010 15:06 | Modified: | 19 Jul 2010 10:34 |
Reporter: | Mike Potjer | Email Updates: | |
Status: | Can't repeat | Impact on me: | |
Category: | MySQL Workbench | Severity: | S1 (Critical) |
Version: | 5.2.25 | OS: | Windows (Win 7 64-bit) |
Assigned to: | CPU Architecture: | Any | |
Tags: | file, lockup, open |
[8 Jul 2010 15:06]
Mike Potjer
[12 Jul 2010 12:24]
Valeriy Kravchuk
I have no problems opening .mwb file uploaded on Mac OS X. It may be Windows 7 specific problem. Please, send the results from Help > System Info menu item.
[12 Jul 2010 14:10]
Mike Potjer
The System Information applet in Windows includes a ton of information. I'm just posting the summary here. If there is something else you need, please be more specific. Thanks. OS Name: Microsoft Windows 7 Enterprise Version: 6.1.7600 Build 7600 Other OS Description: Not Available OS Manufacturer: Microsoft Corporation System Manufacturer: Hewlett-Packard System Model: HP Compaq dc5750 Microtower System Type: x64-based PC Processor: AMD Athlon(tm) Dual Core Processor 4450B, 2300 Mhz, 2 Core(s), 2 Logical Processor(s) BIOS Version/Date: Hewlett-Packard 786E3 v02.34, 4/2/2008 SMBIOS Version: 2.4 Windows Directory: C:\Windows System Directory: C:\Windows\system32 Boot Device: \Device\HarddiskVolume1 Locale: United States Hardware Abstraction Layer: Version = "6.1.7600.16385" Time Zone: Eastern Daylight Time Installed Physical Memory (RAM): 2.00 GB Total Physical Memory: 1.87 GB Available Physical Memory: 805 MB Total Virtual Memory: 3.75 GB Available Virtual Memory: 2.12 GB Page File Space: 1.87 GB Page File: C:\pagefile.sys
[12 Jul 2010 17:06]
MySQL Verification Team
I couldn't repeat on Vista Ultimate X64 too.
[19 Jul 2010 10:34]
Roel Van de Paar
Tested on Win7 HP x64. I have no problems opening .mwb with WorkBench file uploaded (either via file > open model or via doubleclick in OS)
[19 Jul 2010 10:35]
Roel Van de Paar
Marking bug as "can't repeat". If you have additional information that may assist with reproducing this bug, please send.