Bug #35775 Exception when doing double click to a table already opened (Net Framework 2,0 s
Submitted: 2 Apr 2008 17:48 Modified: 2 May 2008 19:13
Reporter: Alberto Tigrera Email Updates:
Status: No Feedback Impact on me:
Category:MySQL Workbench Severity:S3 (Non-critical)
Version:5.0.16 OS:Windows (XP Professional)
Assigned to: CPU Architecture:Any
Tags: AccessViolationException

[2 Apr 2008 17:48] Alberto Tigrera
When doing double click in a table already opened, is sent the following exception:

System.AccessViolationException: Intento de leer o escribir en la memoria protegida. A menudo, esto indica que hay otra memoria daƱada.
   en bec.GRTManager.flush_timers(GRTManager* )
   en MySQL.Workbench.WbContext.flush_timers()
   en MySQL.GUI.Workbench.MainForm.timer_Tick(Object sender, EventArgs e)
   en System.Windows.Forms.Timer.OnTick(EventArgs e)
   en System.Windows.Forms.Timer.TimerNativeWindow.WndProc(Message& m)
   en System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

Single I to want to open the tab to modify the properties of the table because to have several open tabs and the active tab was another tab of a relation.

I hoped that I changed of the tab of the relation to the tab of the properties of the table that already was open but it was not the selected tab.

I have installed the SP1 of Net Framework 2,0 and this totally updated just as my O.S.

How to repeat:
To open the properties of a table, to open the properties of a relation soon to open again the properties of the same table.
[2 Apr 2008 19:13] Valeriy Kravchuk
Thank you for a problem report. Please, upload .mwb file to demonstrate the behaviour described.
[4 Apr 2008 2:41] Alberto Tigrera
File in which work when the error takes place

Attachment: cocacola.mwb (application/octet-stream, text), 9.46 KiB.

[2 May 2008 23: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".