MySQL Bugs: #68696: Performance degradation of MySQL Workbench

Bug #68696	Performance degradation of MySQL Workbench
Submitted:	17 Mar 2013 10:55	Modified:	30 Apr 2013 8:23
Reporter:	Александр Елисеев	Email Updates:
Status:	Can't repeat	Impact on me:	None
Category:	MySQL Workbench	Severity:	S5 (Performance)
Version:	5.2.47 rev 10398	OS:	Linux (OpenSuSE 12.2 with KDE 4.8.5)
Assigned to:		CPU Architecture:	Any
Tags:	performance degradation, reluctance, responsiveness degradation, slow down

Description:
First time after start of the program it responds to mouse clicks and keyboard agile enough. But during the work [with a model for example], edit tables and diagrams, performance and responsiveness to mouse and keyboard degrades to slower and slower. Eventually it makes impossible to make a simple change of the model. I have to close program, and start it again to continue developing of the model.
When I see the taskmanager for mysql-workbench, I see the mysql-workbench-bin as the forked task of catchsegv. 
 Seems the previous version of mysql-workbench had problems with SIGSEGV signal raised because of rmisuse of addres pointer.

How to repeat:
Well, install it, run it, create about 30 tables with 5-10 columns each, create about 5-10 EERdiagrams,  and I beleive you'll meet the same degradation.

Suggested fix:
check for the any address pointer variable to be initialised with NULL, Assigned NULL after deleted dynamic memory object formerly pointed wit the pointer. I beleive it will help to catch any pointer misuses and memory leaks.
 Review the usage and representation of "History" list, maybe the longer it becomes, the more reluctant becomes the program to mouse and keyboard events.

I couldn't repeat with the below hardware System Info (10 ERR and 40 Tables).

MySQL Workbench CE for Linux/Unix version 5.2.47  revision 10398
Configuration Directory: /home/miguel/.mysql/workbench
Data Directory: /usr/share/mysql-workbench
Cairo Version: 1.8.8
OS: Linux 2.6.32-358.6.1.el6.x86_64
CPU: 4x AMD Phenom(tm) 9650 Quad-Core Processor 2300.000 MHz, 7.7 GB RAM
Distribution: CentOS release 6.4 (Final)

Degradation appears if Workbench runs in KDE 4 environment.
If I run it in GNOME, I met degradation not. 
But to run the Workbench in GNOME only is not the acceptable solution.
Because there is a lot of people who use other KDE development tools
and it is not convenient to restart in GNOME for every database development task.