MySQL Bugs: #35635: Heavy lag on the last workbench version

Bug #35635	Heavy lag on the last workbench version
Submitted:	28 Mar 2008 9:11	Modified:	16 May 2008 11:09
Reporter:	moi meme	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Workbench	Severity:	S2 (Serious)
Version:	5.0.17	OS:	Windows
Assigned to:		CPU Architecture:	Any
Tags:	lag, UPDATE

Description:
Since my last update, workbench use 100% of my processor (50% on a dual core).
Without opening any database ...

How to repeat:
Launch workbench

could you give us some detailed info on what system you're using (hardware, operation system, service packs, ... output of Workbench->help->System Info could be helpful too)? I don't see such behaviour on any of our testmachines.
thx

Thank you for the feedback. I can't repeat that behavior in the below hardware:

MySQL Workbench SE for Windows version 5.0.16
Cairo Version: 1.5.12
Rendering Mode: GDI Rendering
OpenGL Driver Version: Not Detected
OS: Windows Vista/2008
CPU: 2x Intel(R) Core(TM)2 CPU         T5500  @ 1.66GHz, 2.0 GB RAM
Video adapter info:
Adapter type: Mobile Intel(R) 945 Express Chipset Family
Chip Type: Intel(R) GMA 950
BIOS String: Intel Video BIOS
Video Memory: 262144 KB

So could you please provide a screen-shot showing the use of CPU before to
launch Workbench and one after that. Thanks in advance.

Workbench now launch with the last opened file.
It continues to consume 100% of one of my two core.
If a click on menu "File" -> "New", I got an error message (see attached screenshot).
If I close workbench interface, a process still survive, that takes 100% of my TWO cores !!!

error message when trying to go in "File" -> "New"

Attachment: wbBug.JPG (image/jpeg, text), 5.77 KiB.

I could not repeat described behavior on dual core computer too. I think cause of the problem can be NVIDIA card.

Im using NVidia with no problems. 
Did the problem exist in 5.0.16?
Does it change anything if you run it from a different user account? (In case it has something
to do with config options)

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