MySQL Bugs: #37602: mysql-proxy ***MEMORY-ERROR***

Bug #37602	mysql-proxy *MEMORY-ERROR*
Submitted:	24 Jun 2008 8:19	Modified:	17 Oct 2009 19:33
Reporter:	jabincn jabincn	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Proxy	Severity:	S3 (Non-critical)
Version:	0.6, 0.6.1	OS:	Linux
Assigned to:		CPU Architecture:	Any

Description:
i think backup my table(mysqldump databasename tablename > tablename.sql),but mysql-proxy error and exit:

***MEMORY-ERROR***: mysql-proxy[6210]: GSlice: failed to allocate 248 bytes (alignment: 256): Cannot allocate memory

How to repeat:
***MEMORY-ERROR***: mysql-proxy[6210]: GSlice: failed to allocate 248 bytes (alignment: 256): Cannot allocate memory

Thank you for the report.

I can not repeat described behavior.

Please indicate:

1. Accurate version of MySQL Proxy you using
2. How do you start MySQL Proxy
3. Accurate command you use to invoke mysqldump
4. If bug is repeatable only with particular table or with any. I.e. if bug is repeatable with example table: CREATE TABLE example(f1 INT);

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".

I get a similar error:
***MEMORY-ERROR***: mysql-proxy[9280]: GSlice: failed to allocate 248 bytes (alignment: 256): Cannot allocate memory

I get this when I do a query that has a large result set (> 1 million rows) 

Version 0.6.1

Foster,

thank you for the feedback.

I can not repeat described behavior with set of 2,000,000 rows. Although with version 0.6.1 I experienced some slowdown which is not the case in current version.

Please try current version 0.7.2 and if problem still exists provide output of SHOW CREATE TABLE problem_table and SHOW TABLE STATUS LIKE 'problem_table'

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".