Bug #64077 MySQL workbench runs away consumming all available memory

Description:
After running the same query multiple times by hitting [ctrl]+[Enter] Workbench becomes unresponsive. Consuming 100% CPU and all available memory.

It have to be killed to regain system control.
Console output:
----------------------------------------------------
$ulimit -Sv 1024000; mysql-workbench --log-level=3
Warning! Can't use connect with timeout in paramiko 1.7.7.1 (George)
Ready.

(mysql-workbench-bin:30159): Gtk-CRITICAL **: gtk_tree_view_unref_tree_helper: assertion `node != NULL' failed

(mysql-workbench-bin:30159): Gtk-CRITICAL **: gtk_tree_view_unref_tree_helper: assertion `node != NULL' failed

(mysql-workbench-bin:30159): Gtk-CRITICAL **: gtk_tree_view_unref_tree_helper: assertion `node != NULL' failed

***MEMORY-ERROR***: mysql-workbench-bin[30159]: GSlice: failed to allocate 496 bytes (alignment: 512): Cannot allocate memory
----------------------------------------------------
wc.log:
----------------------------------------------------
15:26:23 [   Info][      WBContext]: WbContext::init
15:26:23 [   Info][      WBContext]: System info:
        MySQL Workbench CE for Linux/Unix version 5.2.36  revision 8542
        Configuration Directory: /home/user/.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.1.0-1.2-desktop
        CPU: 2x Intel(R) Core(TM)2 Duo CPU     P8700  @ 2.53GHz 2527.248 MHz, 3.8 GB RAM
15:26:23 [   Info][    WQE backend]: Found auto-save workspace /home/user/.mysql/workbench/sql_workspaces/localhost-1.autosave
15:26:25 [   Info][     SSH tunnel]: Starting tunnel
----------------------------------------------------

ulimit is used to prevent workbench from using up all memory.

How to repeat:
Type any query that takes few seconds to execute.
Position cursor inside this query.
Press [ctrl]+[enter] multiple times in rapid succession.

Happens with latest MySQL Workbench CE 5.2.37 8576 as well.

Was able to verify resultsets not being released.

So when is this going to get fixed? It makes this ... software 99% useless!

Seems a duplicate of
http://bugs.mysql.com/bug.php?id=56924

Fixed as of Workbench 5.2.41, and here's the changelog entry:

Quickly executing the same query multiple times would cause
MySQL Workbench to use an excessive amount of memory and CPU.

Happens with latest MySQL Workbench 5.2.41 9727 as well.

I'm using Fedora 20, KDE 4.11 and mySQL Workbench 6.0.9.11421 Build 1170
and I still get this error:
(mysql-workbench-bin:7697): Gtk-CRITICAL **: gtk_tree_view_unref_tree_helper: assertion 'node != NULL' failed

it keeps closing every 2 min. My computer is an i7, 250gb SSD, 16gb DDR3.