Bug #10631 REPAIR TABLE consuming too much RAM
Submitted: 13 May 2005 19:10 Modified: 22 Jun 2005 14:34
Reporter: Dean Ellis Email Updates:
Status: Not a Bug Impact on me:
None 
Category:MySQL Server Severity:S1 (Critical)
Version:4.1.11 OS:Windows (Windows)
Assigned to: Reggie Burnett CPU Architecture:Any

[13 May 2005 19:10] Dean Ellis 
Description:
When using REPAIR TABLE on the attached table, mysqld attempts to allocate hundreds of megabytes of RAM (ultimately trying to allocate approximately 1.5GB).

myisamchk does not allocate so much RAM, nor does using REPAIR TABLE or myisamchk in Linux (or, reportedly, OS X).

How to repeat:
REPAIR TABLE refs

Compare to:
myisamchk -r refs

or compare differences between Windows/Linux.

Suggested fix:
n/a
[17 May 2005 21:15] Brian Aker 
Lowering priority since workaround is possible. We will try to get to this quickly though.
[22 Jun 2005 14:34] Reggie Burnett 
Thank you for taking the time to write to us, but this is not
a bug. Please double-check the documentation available at
http://www.mysql.com/documentation/ and the instructions on
how to report a bug at http://bugs.mysql.com/how-to-report.php

Additional info:

The affected files are corrupt and will attempt to allocate hundreds of megabytes on both Windows and Linux.  I was able to successfully fix the files on Winodws and Linux with enough ram.  Without enough ram, both error out with an out of memory error.