MySQL Workbench 5.0.29 Released

Wasn’t there a release just some days ago, you might ask? Yes, indeed – but we had to create a quick follow-up because a nasty bug found its way through our test and into the recently released 5.0.28. A bit of debug code from our latest canvas changes was left behind and causes Workbench to crash under certain circumstances. Once discovered we found and fixed the root of the problem quite quickly. Additionally we introduced some new icons last time which didn’t find their way into the installer script as well … so frankly its a quickly delieverd follow up to fix 2 things we missed on last release.
We strongly recommend to update to this release asap.

Download version 5.0.29 from our Download Page or – for our SE users – use the integrated update wizard to get you up2date.

9 thoughts on “MySQL Workbench 5.0.29 Released”

  1. We currently have trouble with our publishing system for the SE version. Sorry for the incenveniance, i’ll post a comment when the files are available

  2. Problems resolved – SE customers should now be able to download 5.0.29 via the enterprise portal. (or use your credentials in the update wizard to get and install the update)

  3. installing 5.1.5 on ubuntu 8.10 64 bit

    Organilly I had built ctemplate.092 with workbench 5.1.4 but it would randonly close when adding table or something simlar. So today I saw they released 5.1.5 .. thought I’d give it a try. This time i used ctemplate.09 because thats what their build instructions kept on referring to. Built ctemple, set the LD_LIBRARY_PATH .. built mysql-workbench 5.1.5 (took about 20 minutes on my quad core) It gets stucked on the splash screen and I have to use to kill command to end it… Got the following result:

    * Message: Trying to load module ‘/usr/lib/mysql-workbench/plugins/’ (cpp)
    ** Message: Trying to load module ‘/usr/lib/mysql-workbench/plugins/’ (cpp)
    ** Message: Trying to load module ‘/usr/lib/mysql-workbench/plugins/’ (cpp)
    ** Message: Trying to load module ‘/usr/lib/mysql-workbench/plugins/’ (cpp)
    ** Message: WARNING: Could not get pointer to grt_module_init in module /usr/lib/mysql-workbench/plugins/ (`grt_module_init’: /usr/lib/mysql-workbench/plugins/ undefined symbol: grt_module_init)
    ** Message: WARNING: Could not load Invalid module /usr/lib/mysql-workbench/plugins/
    *** glibc detected *** /usr/bin/mysql-workbench-bin: corrupted double-linked list: 0x000000000108d190 ***
    ======= Backtrace: =========
    ======= Memory map: ========
    00400000-00815000 r-xp 00000000 08:15 2452964 /usr/bin/mysql-workbench-bin
    00a15000-00a1a000 r–p 00415000 08:15 2452964 /usr/bin/mysql-workbench-bin
    00a1a000-00a1e000 rw-p 0041a000 08:15 2452964 /usr/bin/mysql-workbench-bin
    00a1e000-00a21000 rw-p 00a1e000 00:00 0
    00d41000-010aa000 rw-p 00d41000 00:00 0 [heap]
    40168000-40169000 —p 40168000 00:00 0
    40169000-40969000 rwxp 40169000 00:00 0
    409d8000-409da000 rwxp 00000000 00:0e 654 /dev/zero
    7fbcc0000000-7fbcc0021000 rw-p 7fbcc0000000 00:00 0
    7fbcc0021000-7fbcc4000000 —p 7fbcc0021000 00:00 0
    7fbcc6245000-7fbcc6263000 r-xp 00000000 08:15 2810237 /usr/lib/mysql-workbench/plugins/
    7fbcc6263000-7fbcc6463000 —p 0001e000 08:15 2810237 /usr/lib/mysql-workbench/plugins/
    7fbcc6463000-7fbcc6465000 r–p 0001e000 08:15 2810237 /usr/lib/mysql-workbench/plugins/
    7fbcc6465000-7fbcc6466000 rw-p 00020000 08:15 2810237 /usr/lib/mysql-workbench/plugins/
    7fbcc6466000-7fbcc64c6000 r-xp 00000000 08:15 2810230 /usr/lib/mysql-workbench/plugins/
    7fbcc64c6000-7fbcc66c5000 —p 00060000 08:15 2810230 /usr/lib/mysql-workbench/plugins/
    7fbcc66c5000-7fbcc66ce000 r–p 0005f000 08:15 2810230 /usr/lib/mysql-workbench/plugins/
    7fbcc66ce000-7fbcc66cf000 rw-p 00068000 08:15 2810230 /usr/lib/mysql-workbench/plugins/
    7fbcc66cf000-7fbcc66d0000 rw-p 7fbcc66cf000 00:00 0
    7fbcc66d0000-7fbcc6756000 r-xp 00000000 08:15 2810207 /usr/lib/mysql-workbench/plugins/
    7fbcc6756000-7fbcc6955000 —p 00086000 08:15 2810207 /usr/lib/mysql-workbench/plugins/
    7fbcc6955000-7fbcc6959000 r–p 00085000 08:15 2810207 /usr/lib/mysql-workbench/plugins/
    7fbcc6959000-7fbcc695a000 rw-p 00089000 08:15 2810207 /usr/lib/mysql-workbench/plugins/
    7fbcc695a000-7fbcc69e9000 r-xp 00000000 08:15 2810196 /usr/lib/mysql-workbench/plugins/
    7fbcc69e9000-7fbcc6be9000 —p 0008f000 08:15 2810196 /usr/lib/mysql-workbench/plugins/
    7fbcc6be9000-7fbcc6bed000 r–p 0008f000 08:15 2810196 /usr/lib/mysql-workbench/plugins/
    7fbcc6bed000-7fbcc6bee000 rw-p 00093000 08:15 2810196 /usr/lib/mysql-workbench/plugins/
    7fbcc6bee000-7fbcc6bef000 rw-p 7fbcc6bee000 00:00 0
    7fbcc6bef000-7fbcc6cd4000 r-xp 00000000 08:15 2810216 /usr/lib/mysql-workbench/plugins/
    7fbcc6cd4000-7fbcc6ed4000 —p 000e5000 08:15 2810216 /usr/lib/mysql-workbench/plugins/
    7fbcc6ed4000-7fbcc6ee5000 r–p 000e5000 08:15 2810216 /usr/lib/mysql-workbench/plugins/
    7fbcc6ee5000-7fbcc6ee7000 rw-p 000f6000 08:15 2810216 /usr/lib/mysql-workbench/plugins/
    7fbcc6ee7000-7fbcc6ef2000 r-xp 00000000 08:15 2818489 /usr/lib/mysql-workbench/modules/
    7fbcc6ef2000-7fbcc70f2000 —p 0000b000 08:15 2818489 /usr/lib/mysql-workbench/modules/
    7fbcc70f2000-7fbcc70f3000 r–p 0000b000 08:15 2818489 /usr/lib/mysql-workbench/modules/
    7fbcc70f3000-7fbcc70f4000 rw-p 0000c000 08:15 2818489 /usr/lib/mysql-workbench/modules/
    7fbcc70f4000-7fbcc719f000 r-xp 00000000 08:15 2818507 /usr/lib/mysql-workbench/modules/
    7fbcc719f000-7fbcc739e000 —p 000ab000 08:15 2818507 /usr/lib/mysql-workbench/modules/
    7fbcc739e000-7fbcc73a4000 r–p 000aa000 08:15 2818507 /usr/lib/mysql-workbench/modules/
    7fbcc73a4000-7fbcc73a6000 rw-p 000b0000 08:15 2818507 /usr/lib/mysql-workbench/modules/
    7fbcc73a6000-7fbcc73fa000 r-xp 00000000 08:15 2818490 /usr/lib/mysql-workbench/modules/
    7fbcc73fa000-7fbcc75fa000 —p 00054000 08:15 2818490 /usr/lib/mysql-workbench/modules/
    7fbcc75fa000-7fbcc75fd000 r–p 00054000 08:15 2818490 /usr/lib/mysql-workbench/modules/
    7fbcc75fd000-7fbcc75fe000 rw-p 00057000 08:15 2818490 /usr/lib/mysql-workbench/modules/
    7fbcc75fe000-7fbcc7606000 r-xp 00000000 08:15 2818473 /usr/lib/mysql-workbench/modules/
    7fbcc7606000-7fbcc7806000 —p 00008000 08:15 2818473 /usr/lib/mysql-workbench/modules/
    7fbcc7806000-7fbcc7807000 r–p 00008000 08:15 2818473 /usr/lib/mysql-workbench/modules/
    7fbcc7807000-7fbcc7808000 rw-p 00009000 08:15 2818473 /usr/lib/mysql-workbench/modules/
    7fbcc7808000-7fbcc787f000 r-xp 00000000 08:15 2818488 /usr/lib/mysql-workbench/modules/
    7fbcc787f000-7fbcc7a7e000 —p 00077000 08:15 2818488 /usr/lib/mysql-workbench/modules/
    7fbcc7a7e000-7fbcc7a81000 r–p 00076000 08:15 2818488 /usr/lib/mysql-workbench/modules/
    7fbcc7a81000-7fbcc7a82000 rw-p 00079000 08:15 2818488 /usr/lib/mysql-workbench/modules/

  4. I run Workbench SE on Windows Vista 64 and during the last few updates I have found that the update process crashes windows installer (Data Executon Prevention has closed windows installer …). Interestingly I have also noticed this with the GUI tools updates r14 and r15.
    I can often solve it by downloading the file directly and using this, though I usually have to install it twice! For Workbench 5.0.29 there is no file to download from the Enterprise Portal as yet, so I cannot fully test this hypothesis.

  5. I have Vista 32. I’m having problems running the latest workbench se 5.0.29. I’ve got twice an error message “Access violation – no RTTI data!” I reported to MYSQL via bug report form (Bug #41457). I have a file containing 3 EER diagrams. When I click in one of them I don’t seem to have a problem, but as I begin to click on the other tabs, back and forth, as I work with the diagrams, I get the error message. When this happens, I cannot any longer work on that diagram for it becomes unavailable. Could this be related to the prior issue with 5.0.28?


  6. I’m working with 5.0.29 and have a model with 35 tables.

    When I click a table for modification or move the element into de model my computer lost performance and WB take a while to respond (enought to desesperate in daily use).

    Have a tips page to check posible reasons or tips for a better performance?.

    My pc have a Intel dual CPU E210 2GHz and 2MB RAM, then I thinks that is enougth for run a normal program.

    Please send me tips.

  7. rolivares,

    Can you report a bug to with your model attached and give the exact steps needed to cause such a slow down? If it takes a long time to get it to that stage, what kind of stuff do you do while working? Can you also try reducing the number of Undo steps to about 10 in Tools -> Preferences and see if that helps?

Leave a Reply