MySQL Bugs: #59170: Error during New Server Instance, Attempted to read or write protected memory

Bug #59170	Error during New Server Instance, Attempted to read or write protected memory
Submitted:	25 Dec 2010 20:08	Modified:	15 Jan 2011 8:53
Reporter:	David Williams	Email Updates:
Status:	Duplicate	Impact on me:	None
Category:	MySQL Workbench: Administration	Severity:	S3 (Non-critical)
Version:	5.2.31 Rev7115	OS:	Windows (Vista 32bit SP2)
Assigned to:		CPU Architecture:	Any

Description:
Crash during New Server Instance
Specify Host Machine - localhost
Database Connection - port 5000
Test DB Connection - 
  Open Database Connection
  Get Server Version: 5.1.47-ndb-7.1.5-cluster-gpl
  Get Server OS: Windows
  Database connection tested successfully
Clicking Next goes to Set Windows configuration parameters for this machine
MySQL Workbench Unexpected Error windows pops up
MySQL Workbench has encountered a problem
Attempted to read or write protected memory. This is often an indication that other memory is corrupt.

How to repeat:
make a New Server Instance
Specify Host Machine - localhost
Database Connection - port 5000
Test DB Connection - 
Click Next

The MySQL server is using the port 5000?. Thanks in advance.

Yes, MySQL server (cluster) is port 5000.

When you'll get this error next time, please, right click somewhere in the error dialog box without text and use Copy stack trace to clipboard context menu item to get the stack trace. Send it to this bug report.

stack trace

Attachment: MySQLWorkbenchStackTrace1.txt (text/plain), 1.58 KiB.

Verified connecting with Mint Debian host server.

Ditto on Windows 2008 R2 connecting to a local database.  Dies same place, "Set Windows Configuration parameters for this machine"..  Database itself can be managed just fine via CLI mysql.exe.  

Exception = System.AccessViolationException
Message = Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
FullText = System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
   at std.basic_string<char,std::char_traits<char>,std::allocator<char> >.c_str(basic_string<char\,std::char_traits<char>\,std::allocator<char> >* )
   at MySQL.?A0x4861a96a.CppStringToNative(basic_string<char\,std::char_traits<char>\,std::allocator<char> >* str)
   at MySQL.Forms.TextEntryImpl.set_text(TextEntry* self, basic_string<char\,std::char_traits<char>\,std::allocator<char> >* text)
   at MySQL.MCallback2<void\,mforms::TextEntry \*\,std::basic_string<char\,std::char_traits<char>\,std::allocator<char> > const \&>.cpp_callback(TextEntry* a1, basic_string<char\,std::char_traits<char>\,std::allocator<char> >* a2)
   at sigc.internal.signal_emit0<void,sigc::nil>.emit(signal_impl* impl)
   at sigc.signal0<void,sigc::nil>.emit(signal0<void\,sigc::nil>* )
   at mforms.Wizard.next_clicked(Wizard* )
   at MySQL.Forms.WizardImpl.nextClick(Object sender, EventArgs arguments)
   at System.Windows.Forms.Control.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnClick(EventArgs e)
   at System.Windows.Forms.Button.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

Also just a comment, this appears to be a change / regression between 5.2.30 and 5.2.31.  Just re-installed 5.2.30 and works just fine.  Granted I also don't get that particular window during the wizard (where you set the configuration file) but the wizard completes and you can edit post-wizard via edit server instance.

It looks like this feature was added to the wizard in 31 and is basically buggy.

this is a duplicate of Bug #59118

More information:
Being new to MySQL Cluster (and MySQL Workbench) I originally followed the "MySQL Cluster Quick Start for Windows" ( http://downloads.mysql.com/tutorials/cluster/GetMySQLClusterRunning-Windows.pdf ). The procedure doesn't register MySQL as a Windows service. After installing MySQL 5.5, the error did not occur. But only the second version of MySQL showed up in the wizard.

After deleting the Windows registry key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MySQL5 and rebooting, the error returned.

I put the cluster server as a service ( c:\Users\admin\mysqlc\bin\mysqld --install-manual MySQL51c --defaults-file=C:\Users\admin\my_cluster\conf\my.cnf ) from an Administrator command prompt shell, and the error did not occur.

In the process of fiddling, I encountered a different error at the same spot in the wizard. If MySQL was registered as a service, and either the name of the Services key or the DisplayName value were changed, a System.OutOfMemoryException popped up.