#25 Memory hole and crash during mysql dumps

[Kristofer Widholm]

Hi, I just posted this to macupdate.com, and then
thought it was better to put it where it belongs: in
the bug channel!

Still my favorite graphical interface to MySQL
databases. Thanks to the developers for their work.

I still have one MAJOR flaw to point out. Do a MySQL
table dump with drop tables on even a medium sized
database (50,000 rows, four tables), and prepared to
see CocoaMySQL hang (reports 101% processor usage and
becomes unresponsive and gobbles up massive amounts of
RAM until you force quit it).

This behavior has been verified on three different Macs
(PowerPC and Intel) with different OS versions since at
least the 0.5 days in CocoaMySQL, and it still exists!

I love CocoaMySQL, but am sad that I still need to use
the command line for any data lifting of substance.

Suggestion: Feed the mysqldump to a shell subprocess
and just let it notify the application when it is done.
This would free up the user interface in the meantime
and would handle the memory issues.

Steps to reproduce:
1. Connect to any MySQL database (version 3.x, 4.x, or
5.x) of medium size (50,000 rows or thereabouts should
be sufficient).
2. Select File:Export:Cocoa MySQL dump
3. Make sure all tables in the database are selected
(default), and choose "Add drop table".
4. Click OK and watch MySQL start gobble memory and
hang forever in Activity Monitor.

Again, this happens on Panther systems, Tiger systems,
both PowerPC and Intel, and on all databases I've tried
it on as long as there is a table or two of medium size.