MySQL Bugs: #21332: Memory not released after truncate or drop table

Bug #21332	Memory not released after truncate or drop table
Submitted:	28 Jul 2006 16:39	Modified:	28 Aug 2006 23:06
Reporter:	Bill Willits	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Server	Severity:	S3 (Non-critical)
Version:	5.0.19	OS:	Linux (CentOS (Linux))
Assigned to:	Assigned Account	CPU Architecture:	Any
Tags:	Memory, reclaim

Description:
When creating, populating and dropping Memory tables, the memory utilization by the mysqld process continually increases until all memory is exhausted and the server crashes.

It seems that the memory that should be freed by dropped or truncated tables is not reused by subsequent table creation/population operations.  This is also evident when creating and dropping indexes on Memory tables.

I realize that unix will not release the memory back to the OS after creating and dropping the table, but subsequent create and population operations should be able to use the memory freed up within the myslqd address space.

How to repeat:
Create a memory table and populate it with data.
Record the memory utilization of the mysqld process.
Drop the table
Create and repopulate the table with the same dataset.
The memory usage will increase instead of remaining the same.

Thank you for the report.

Current version of MySQL 5.0 is 5.0.23. Could you please try to repeat the problem using new version available at http://www.mysql.com/downloads/?

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".