I am running MySQL 4.1 on Windows XP, with 1 GB memory, 4GB pagefile space
and a database of around 1GB.
Apparently, a 1GB database is more than MySQL Admin can handle, and any
attempt to store or restore a backup ends-up with either backup or
Restore/"Analyzing Backup File" stopping way before the end of the backup
file (showing no contents). This is in the best case - sometimes MySQL Admin
fails with an error about not being able to allocate memory and terminates
abnormally.
Windows Task Manager indeed shows almost no physical memory left while MySQL
Admin is working, then all of this memory gets freed when MySQL Admin bombs
or is closed.
I have filed a bug against MySQL Admin and waiting to hear back but, in the
meantime, is there a way via MySQL Server configuation parameters to reign
in the memory MySQL Admin consumes?