Bug #63943 Crash when try to synchronize model
Submitted: 6 Jan 2012 5:06 Modified: 26 Mar 2012 7:13
Reporter: Sukung Montross Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Workbench: Modeling Severity:S2 (Serious)
Version:5.2.37 OS:Linux (Ubuntu 11.04)
Assigned to: CPU Architecture:Any
Tags: corruption, crash, diagram, glibc, large, malloc, Memory, model, synchronize

[6 Jan 2012 5:06] Sukung Montross
Description:
When attempting to synchronize a model, Workbench crashes completely when clicking on “next” after the “Fetch Object Info” stage has completed.

# CRASH MESSAGE #
*** glibc detected *** /usr/bin/mysql-workbench-bin: malloc(): memory corruption: 0x0bb2c208 ***

Note* This happened to Window7x64 too -- same crash
Note* This happened since MySQL Workbench v5.2.34 , I had search in bug report for similar case but most in staus -no feedback- 

How to repeat:
In my case, I have a diagram containing 158 tables (create from ERR model from existing database with successful).

My connection is via tunneled SSH. 

To repeat the crash, all I need to do is synchronize the model.  Workbench crashes as described above. Nothing wrote to wb.log

Suggested fix:
Seem it's happened to diagram that have many tables & relations.
From my guess -- it crash when try to parser model and compare between local and remote.

Note* 5.2.37 working well with small diagram 

Thanks
[8 Jan 2012 18:58] Valeriy Kravchuk
How many tables do you have in your model, and what exact server version, 5.x.y, are you trying to synchronize with?
[9 Jan 2012 8:48] Sukung Montross
the model has 150+ tables and now i'm using MySQL v5.5.13 (v5.1 have this problem too)

Note* It successful it try to sync to empty remote database

but after remote database have tables -- it'll crash if i have enter compare tables process.

Thanks you.
[13 Jan 2012 11:54] Valeriy Kravchuk
Please, send the output of Help > System Info menu item. I wonder how much RAM do you have.
[16 Jan 2012 9:42] Sukung Montross
I had copy system info of both my computers
sorry for used version 5.2.36 on windows 
-- but both crash since 5.2.34

System Info (Linux)
==========================================================
MySQL Workbench CE for Linux/Unix version 5.2.37  revision 8576
Configuration Directory: /home/sukung/.mysql/workbench
Data Directory: /usr/share/mysql-workbench
Cairo Version: 1.10.2
Rendering Mode: OpenGL is not available on this system, so Native is used for rendering.
OS: Linux 3.0.0-14-generic-pae
CPU: 4x Intel(R) Core(TM) i5 CPU       M 460  @ 2.53GHz 1199.000 MHz, 3.8 GB RAM

System Info  (Windows 7) 
======================================================
MySQL Workbench CE for Windows version 5.2.36  revision 8542
Configuration Directory: C:\Users\Sukung\AppData\Roaming\MySQL\Workbench
Data Directory: C:\Program Files (x86)\MySQL\MySQL Workbench 5.2 CE
Cairo Version: 1.8.8
Rendering Mode: OpenGL is not available on this system, so GDI is used for rendering.
OS: Microsoft Windows 7 Ultimate Edition Service Pack 1 (build 7601), 64-bit
CPU: 8x Intel(R) Core(TM) i7 CPU         920  @ 2.67GHz, 6.0 GiB RAM
Active video adapter (0): ATI Radeon HD 5700 Series
Installed video RAM: 1024 MB
Current video mode: 1920 x 1080 x 4294967296 colors
Used bit depth: 32
Driver version: 8.920.0.0
Installed display drivers: aticfx64.dll,aticfx64.dll,aticfx64.dll,aticfx32,aticfx32,aticfx32,atiumd64.dll,atidxx64.dll,atidxx64.dll,atiumdag,atidxx32,atidxx32,atiumdva,atiumd6a.cap,atitmm64.dll
Current user language: Thai (Thailand)
[14 Feb 2012 15:08] MySQL Verification Team
Could you please provide the model project file private if you wish?. Thanks.
[24 Feb 2012 15:25] Armando Lopez Valencia
Thanks  a lot for your report.
Verified in:
Client: Ubuntu 11.04x64 (SSH connection)
Server: Ubuntu 10.04x86
WB 5.2.38 rev 8753

Repro steps:
1. Open WB.
2. Open the model provided by the reporter.
3. Synchronize the model with the remote DB (Shift+Ctrl+Z).
4. Modify the model.
5. Synchronize the model again (Shift+Ctrl+Z).

Actual results:
WB crash.
[26 Mar 2012 7:13] Philip Olson
Fixed as of 5.2.39, and here's the changelog:

The following sequence could crash Workbench: "Open a model",
"Synchronize the model with a remote database", "Modify the
model", and then "Synchronize the model" a second time.