MySQL Bugs: #66858: refresh all tables on remote database schema

Bug #66858	refresh all tables on remote database schema
Submitted:	18 Sep 2012 14:16	Modified:	18 Oct 2012 15:40
Reporter:	Frederik Pfisterer	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Workbench	Severity:	S3 (Non-critical)
Version:	5.2.42	OS:	Windows (Microsoft Windows 7 Service Pack 1 (build 7601), 64-bit)
Assigned to:		CPU Architecture:	Any
Tags:	WBBugReporter

Description:
simple right click on a remote database schema hitting "refresh all" 

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

MySQL Workbench CE for Windows version 5.2.42  revision 9752
Configuration Directory: C:\Users\fredpfi\AppData\Roaming\MySQL\Workbench
Data Directory: C:\Program Files (x86)\MySQL\MySQL Workbench 5.2 CE
Cairo Version: 1.8.8
OS: Microsoft Windows 7  Service Pack 1 (build 7601), 64-bit
CPU: 4x Intel(R) Core(TM) i5 CPU         750  @ 2.67GHz, 8.0 GiB RAM
Active video adapter (0): NVIDIA GeForce GTS 250
Installed video RAM: 1024 MB
Current video mode: 1920 x 1080 x 4294967296 Farben
Used bit depth: 32
Driver version: 8.16.11.9062
Installed display drivers: nvd3dumx.dll,nvwgf2umx.dll,nvwgf2umx.dll,nvd3dum,nvwgf2um,nvwgf2um
Current user language: Deutsch (Deutschland)

Exception = MySQL.Grt.BackendException
Message = Attempt to dereference NULL TreeNode
FullText = MySQL.Grt.BackendException: Attempt to dereference NULL TreeNode
   bei MySQL.Workbench.WbContext.flush_idle_tasks()
   bei MySQL.GUI.Workbench.Program.timer_Tick(Object sender, EventArgs e)

How to repeat:
right click on database schema when connected to a remote server and hit "refresh all"

Please try version 5.2.43. Thanks.

[18 Sep 14:56] Miguel Solorzano

Please try version 5.2.43. Thanks.

-> thanks will try but "check updates" in workbench is saying "you are already using the latest version"

Thank you for the feedback. You are reporting 5.2.42 and the check update failed, anyway try to download 5.2.43 from:

http://dev.mysql.com/downloads/workbench/5.2.html

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