MySQL Bugs: #66293: Crashes when trying to see register list

Bug #66293	Crashes when trying to see register list
Submitted:	10 Aug 2012 0:07	Modified:	3 Oct 2012 14:58
Reporter:	Nahuel Sotelo	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Workbench	Severity:	S3 (Non-critical)
Version:	5.2.41	OS:	Windows (Microsoft Windows 7 Ultimate Edition Service Pack 1 (build 7601), 64-bit)
Assigned to:		CPU Architecture:	Any
Tags:	WBBugReporter

Description:
Just tried to see the list of register from a table and the program crashes

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

MySQL Workbench CE for Windows version 5.2.41  revision 9727
Configuration Directory: C:\Users\NiS\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 Ultimate Edition Service Pack 1 (build 7601), 64-bit
CPU: 2x AMD Turion(tm) X2 Dual-Core Mobile RM-72, 3.8 GiB RAM
Active video adapter (0): LogMeIn Mirror Driver
Installed video RAM: 0 MB
Current video mode: 1440 x 900 x 4294967296 colores
Used bit depth: 32
Driver version: 7.1.542.0
Installed display drivers: NULL
Current user language: Español (Argentina)

Exception = System.ArgumentOutOfRangeException
Message = El índice estaba fuera del intervalo. Debe ser un valor no negativo e inferior al tamaño de la colección.
Nombre del parámetro: index
FullText = System.ArgumentOutOfRangeException: El índice estaba fuera del intervalo. Debe ser un valor no negativo e inferior al tamaño de la colección.
Nombre del parámetro: index
   en System.Windows.Forms.Control.MarshaledInvoke(Control caller, Delegate method, Object[] args, Boolean synchronous)
   en System.Windows.Forms.Control.Invoke(Delegate method, Object[] args)
   en System.Windows.Forms.Control.Invoke(Delegate method)
   en MySQL.GUI.Workbench.SqlIdeForm.RecordsetListChanged(Int32 editor_index, Int64 key, Boolean added)
   en MySQL.Grt.RunWrappedDelegate3<void\,void\,int\,int\,boost::shared_ptr<Recordset>\,__int64\,bool\,bool\,MySQL::Grt::DelegateSlot3<void\,void\,int\,int\,boost::shared_ptr<Recordset>\,__int64\,bool\,bool>::ManagedDelegate>.native_callback(Int32* a1, shared_ptr<Recordset>* a2, Boolean* a3)
   en boost.detail.function.void_function_invoker3<void (__cdecl*)(int const &,boost::shared_ptr<Recordset> const &,bool const &),void,int const &,boost::shared_ptr<Recordset> const &,bool const &>.invoke(function_buffer* function_ptr, Int32* a0, shared_ptr<Recordset>* a1, Boolean* a2)
   en boost.function3<void,int const &,boost::shared_ptr<Recordset> const &,bool const &>.()(function3<void\,int const \&\,boost::shared_ptr<Recordset> const \&\,bool const \&>* , Int32* a0, shared_ptr<Recordset>* a1, Boolean* a2)
   en boost.detail.function.void_function_obj_invoker3<boost::function<void __cdecl(int const &,boost::shared_ptr<Recordset> const &,bool const &)>,void,int,boost::shared_ptr<Recordset>,bool>.invoke(function_buffer* function_obj_ptr, Int32 a0, shared_ptr<Recordset>* a1, Boolean a2)

How to repeat:
Open a database, then try to see a table list.

What exact server version, 5.x.y, are you working with? How many tables do you have there?

I'm working locally with XAMPP 1.7.3 and the server version of PHPMyAdmin is 5.1.41

Please try version 5.2.42. Thanks.

Ok. Thanks for the "solution".

It was not a solution, but we do not fix bugs if they are NOT repeatable with a recent version. 

Obviously there were no problem in our case to open any database even with 5.2.41, so looks like the problem is easily repeatable only in your environment. That's why it would be useful to know if, in your environment, 5.2.42 works any differently before trying to proceed any further with this bug report.

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

I didn't say anything else 'cause I don't want to change any of my server configuration unless it's actually necessary. In the contrary case, I rather prefer use another software... wouldn't you do the same?

Anyway, on 5.2.42 seems to be fixed. It didn't crashed until now while using this feature.

Please feel free to re-open this bug if the problem persist.
Thanks.