Bug #34658 An unhandled exception of type 'System.NullReferenceException'
Submitted: 19 Feb 2008 9:58 Modified: 28 Mar 2008 14:44
Reporter: Serge Adda Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Workbench Severity:S1 (Critical)
Version:MySQL Workbench 5.0.13 SE Beta OS:Microsoft Windows (Vista SP1 x64)
Assigned to: CPU Architecture:Any
Tags: NullReferenceException

[19 Feb 2008 9:58] Serge Adda
Description:
When launching the application, I get a crash:

Call Stack:
System.Windows.Forms.dll!System.Windows.Forms.VScrollBar.DefaultSize.get() + 0x11 bytes	
 	System.Windows.Forms.dll!System.Windows.Forms.Control.Control(bool autoInstallSyncContext = true) + 0x1ae bytes	
 	System.Windows.Forms.dll!System.Windows.Forms.ScrollBar.ScrollBar() + 0x34 bytes	
 	System.Windows.Forms.dll!System.Windows.Forms.VScrollBar.VScrollBar() + 0x5 bytes	
 	Aga.Controls.dll!Aga.Controls.Tree.TreeViewAdv.InitializeComponent() + 0x23 bytes	
>	Aga.Controls.dll!Aga.Controls.Tree.TreeViewAdv.TreeViewAdv() + 0xf3 bytes	
 	MySQLWorkbench.exe!MySQL.GUI.Workbench.ModelLayerForm.InitializeComponent() + 0xae bytes	
 	MySQLWorkbench.exe!MySQL.GUI.Workbench.ModelLayerForm.ModelLayerForm() + 0x3a bytes	
 	MySQLWorkbench.exe!MySQL.GUI.Workbench.ModelLayerForm.ModelLayerForm(MySQL.Workbench.WbContext WbContext = {MySQL.Workbench.WbContext}) + 0x1d bytes	
 	MySQLWorkbench.exe!MySQL.GUI.Workbench.MainForm.MainForm(MySQL.Workbench.WbContext WbContext = {MySQL.Workbench.WbContext}) + 0x8f bytes	
 	MySQLWorkbench.exe!MySQL.GUI.Workbench.Program.Main(string[] Args = {string[0]}) + 0x665 bytes	
 	
 	
Debugger Output:
'MySQLWorkbench.exe' (Managed): Loaded 'C:\Windows\assembly\GAC_32\mscorlib\2.0.0.0__b77a5c561934e089\mscorlib.dll', Symbols loaded.
'MySQLWorkbench.exe' (Managed): Loaded 'D:\mySQL\MySQL Workbench 5.0.13 SE Beta\MySQLWorkbench.exe'
'MySQLWorkbench.exe' (Managed): Loaded 'D:\mySQL\MySQL Workbench 5.0.13 SE Beta\wb.wr.dll'
'MySQLWorkbench.exe' (Managed): Loaded 'D:\mySQL\MySQL Workbench 5.0.13 SE Beta\grt.wr.dll'
'MySQLWorkbench.exe' (Managed): Loaded 'C:\Windows\assembly\GAC_MSIL\System.Windows.Forms\2.0.0.0__b77a5c561934e089\System.Windows.Forms.dll', Symbols loaded.
'MySQLWorkbench.exe' (Managed): Loaded 'C:\Windows\assembly\GAC_MSIL\System\2.0.0.0__b77a5c561934e089\System.dll', Symbols loaded.
'MySQLWorkbench.exe' (Managed): Loaded 'C:\Windows\assembly\GAC_MSIL\System.Drawing\2.0.0.0__b03f5f7f11d50a3a\System.Drawing.dll', Symbols loaded.
'MySQLWorkbench.exe' (Managed): Loaded 'D:\mySQL\MySQL Workbench 5.0.13 SE Beta\MySQLCsUtilities.dll'
'MySQLWorkbench.exe' (Managed): Loaded 'C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.1434_none_d08b6002442c891f\msvcm80.dll', Symbols loaded.
'MySQLWorkbench.exe' (Managed): Loaded 'D:\mySQL\MySQL Workbench 5.0.13 SE Beta\MySQLGrtShell.exe'
'MySQLWorkbench.exe' (Managed): Loaded 'D:\mySQL\MySQL Workbench 5.0.13 SE Beta\WeifenLuo.WinFormsUI.Docking.dll'
'MySQLWorkbench.exe' (Managed): Loaded 'C:\Windows\assembly\GAC_MSIL\System.Xml\2.0.0.0__b77a5c561934e089\System.Xml.dll', Symbols loaded.
'MySQLWorkbench.exe' (Managed): Loaded 'C:\Windows\assembly\GAC_MSIL\System.Configuration\2.0.0.0__b03f5f7f11d50a3a\System.Configuration.dll', Symbols loaded.
'MySQLWorkbench.exe' (Managed): Loaded 'D:\mySQL\MySQL Workbench 5.0.13 SE Beta\MySQLWorkbenchEditors.dll'
'MySQLWorkbench.exe' (Managed): Loaded 'D:\mySQL\MySQL Workbench 5.0.13 SE Beta\Aga.Controls.dll'
An unhandled exception of type 'System.NullReferenceException' occurred in System.Windows.Forms.dll

Additional information: Object reference not set to an instance of an object.

How to repeat:
Just launch the application
[22 Feb 2008 13:20] Serge Adda
This is Vista SP1!
[28 Feb 2008 14:44] Johannes Taxacher
Hello Serge,

could you please check again using the latest beta release (5.0.14a)? we we're unable to reproduce on our vista machines.

thx
[29 Mar 2008 0: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".