MySQL Bugs: #66459: crash on synchronize model

Bug #66459	crash on synchronize model
Submitted:	20 Aug 2012 2:27	Modified:	13 Oct 2012 16:35
Reporter:	Bogdan Fürst	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Workbench: Modeling	Severity:	S3 (Non-critical)
Version:	5.2.42	OS:	Windows (Microsoft Windows 7 Ultimate Edition (build 7600), 64-bit)
Assigned to:		CPU Architecture:	Any
Tags:	WBBugReporter

Description:
crashed when entering 'Model and Database Differences'

----- Developer Notes -----

MySQL Workbench CE for Windows version 5.2.42  revision 9752
Configuration Directory: C:\Users\AI\AppData\Roaming\MySQL\Workbench
Data Directory: C:\Program Files (x86)\MySQL\MySQL Workbench CE 5.2.42
Cairo Version: 1.8.8
OS: Microsoft Windows 7 Ultimate Edition (build 7600), 64-bit
CPU: 8x Intel(R) Core(TM) i7 CPU         920  @ 2.67GHz, 6.0 GiB RAM
Active video adapter (0): ATI Radeon HD 5800 Series
Installed video RAM: 1024 MB
Current video mode: 1920 x 1200 x 4294967296 colors
Used bit depth: 32
Driver version: 8.982.0.0
Installed display drivers: aticfx64.dll,aticfx64.dll,aticfx64.dll,aticfx32,aticfx32,aticfx32,atiumd64.dll,atidxx64.dll,atidxx64.dll,atiumdag,atidxx32,atidxx32,atiumdva,atiumd6a.cap,atitmm64.dll
Current user language: Slovenian (Slovenia)

Exception = System.Threading.ThreadStateException
Message = Thread is running or terminated; it cannot restart.
FullText = System.Threading.ThreadStateException: Thread is running or terminated; it cannot restart.
   at System.Threading.Thread.StartInternal(IPrincipal principal, StackCrawlMark& stackMark)
   at System.Threading.Thread.Start(StackCrawlMark& stackMark)
   at System.Threading.Thread.Start()
   at Aga.Controls.Tree.NodeControls.ExpandingIcon.Start()
   at Aga.Controls.Tree.TreeViewAdv.AddExpandingNode(TreeNodeAdv node)
   at Aga.Controls.Tree.TreeViewAdv.SetIsExpanded(TreeNodeAdv node, Boolean value)
   at Aga.Controls.Tree.TreeViewAdv.SetIsExpanded(ExpandArgs eargs)
   at Aga.Controls.Tree.TreeViewAdv.<SetIsExpanded>b__23(Object argument)
   at Aga.Controls.Threading.AbortableThreadPool.<>c__DisplayClass5.<HandleItem>b__3(Object )
   at System.Threading.ExecutionContext.runTryCode(Object userData)
   at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean ignoreSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at Aga.Controls.Threading.AbortableThreadPool.HandleItem(Object ignored)
   at System.Threading.QueueUserWorkItemCallback.WaitCallback_Context(Object state)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean ignoreSyncCtx)
   at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
   at System.Threading.ThreadPoolWorkQueue.Dispatch()
   at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback()

How to repeat:
first time occurence, no idea how to repeat

may be related to 
http://bugs.mysql.com/bug.php?id=66380

managed to repeat the issue after restarting workbench: 
1 edit view by double click on view item
2 modify part of select in view from
IF(
 ISNULL(sa.`Row`), 
  NULL, 		
  CONCAT(az.`Code`, ' (', CHAR(sa.`Row` + 65 USING utf8), ' ', sa.`Column` + 1, ') ', m.`Name`)
) AS xxx
into

IF(
 ISNULL(sa.`Row`), 
  NULL, 		
  CONCAT(az.`Code`, ', ', m.`Name`, ', ', CHAR(sa.`Row` + 65 USING utf8), '-', sa.`Column` + 1)
) AS xxx
3 Database -> Synchronize model... crash on diff dialog

The issue seems to occur only if synchornize model is not executed after starting workbench and before editing the view.

Bug #66380 is a duplicate

Please try version 5.2.43 . Thanks.

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".