Bug #65996 Crash on drop schema
Submitted: 24 Jul 2012 11:03 Modified: 20 Aug 2012 13:43
Reporter: Mykhailo Oleksiuk Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Workbench: SQL Editor Severity:S2 (Serious)
Version:5.2.40 OS:Windows (Windows 7, OS Version: 6.1.7601 Service Pack 1 Build 7601, 64-bit)
Assigned to: CPU Architecture:Any
Tags: crash, drop schema

[24 Jul 2012 11:03] Mykhailo Oleksiuk
Description:
Mysql Workbench crashes on dropping db schema.

Mysql Workbench is installed on Win7 64bit SP1:
Version: 5.2.40

Mysql server is installed on VMware:
SHOW VARIABLES LIKE "%version%";
'protocol_version', '10'
'version', '5.0.77'
'version_bdb', 'Sleepycat Software: Berkeley DB 4.1.24: (January 29, 2009)'
'version_comment', 'Source distribution'
'version_compile_machine', 'x86_64'
'version_compile_os', 'redhat-linux-gnu'

Linux version 2.6.18-194.3.1.el5 (mockbuild@builder10.centos.org) (gcc version 
4.1.2 20080704 (Red Hat 4.1.2-48)) #1 SMP Thu May 13 13:08:30 EDT 2010

How to repeat:
1.Open attached sql script or EER Model.
2.Execute sql script to create db schema.
3.Click refresh button to see a newly create schema in tree view;
4.Right click on a newly create schema -> Drop Schema...
5.Go through wizard and press Finish.

Expected result:
Mysql Workbench shouldn't crash.

Actual result:
Mysql Workbench crashes.
[24 Jul 2012 11:04] Mykhailo Oleksiuk
eer model

Attachment: crash_on_drop_schema.mwb (application/octet-stream, text), 9.86 KiB.

[24 Jul 2012 11:04] Mykhailo Oleksiuk
sql script

Attachment: crash_on_drop_schema.sql (application/octet-stream, text), 5.17 KiB.

[24 Jul 2012 13:28] Valeriy Kravchuk
I was not able to repeat the crash while working with a newer version version, 5.0.97. I wonder if there is anything noted in the Event Viewer logs at OS level for the crash.
[24 Jul 2012 13:41] Mykhailo Oleksiuk
Event Viewer has two errors:
1.NET Runtime
Application: MySQLWorkbench.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.AccessViolationException
Stack:
   at <Module>.wb.WBContext.flush_idle_tasks(wb.WBContext*)
   at MySQL.Workbench.WbContext.flush_idle_tasks()
   at MySQL.GUI.Workbench.Program.timer_Tick(System.Object, System.EventArgs)
   at System.Windows.Forms.Timer.OnTick(System.EventArgs)
   at System.Windows.Forms.Timer+TimerNativeWindow.WndProc(System.Windows.Forms.Message ByRef)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr, Int32, IntPtr, IntPtr)
   at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG ByRef)
   at System.Windows.Forms.Application+ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(IntPtr, Int32, Int32)
   at System.Windows.Forms.Application+ThreadContext.RunMessageLoopInner(Int32, System.Windows.Forms.ApplicationContext)
   at System.Windows.Forms.Application+ThreadContext.RunMessageLoop(Int32, System.Windows.Forms.ApplicationContext)
   at System.Windows.Forms.Application.Run(System.Windows.Forms.ApplicationContext)
   at MySQL.GUI.Workbench.Program.Main(System.String[])

2.Application Error
Faulting application name: MySQLWorkbench.exe, version: 5.2.40.8790, time stamp: 0x4fa2f938
Faulting module name: wbprivate.be.dll, version: 0.0.0.0, time stamp: 0x4fa2f597
Exception code: 0xc0000005
Fault offset: 0x00001053
Faulting process id: 0x1288
Faulting application start time: 0x01cd6989e4611a81
Faulting application path: C:\Program Files (x86)\MySQL\MySQL Workbench 5.2 CE\MySQLWorkbench.exe
Faulting module path: C:\Program Files (x86)\MySQL\MySQL Workbench 5.2 CE\wbprivate.be.dll
Report Id: ab374411-d594-11e1-b3cd-005056c00008
[20 Aug 2012 13:43] Mykhailo Oleksiuk
Not reproducible from 5.2.42.