MySQL Bugs: #64032: Bad Allocation on execute SQL-MYSQL

Bug #64032	Bad Allocation on execute SQL-MYSQL
Submitted:	14 Jan 2012 12:29	Modified:	15 Feb 2012 9:12
Reporter:	a b	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Workbench: SQL Editor	Severity:	S1 (Critical)
Version:	5.2.35	OS:	Windows
Assigned to:		CPU Architecture:	Any
Tags:	Bad Allocation

Description:
Hi

i am trying to execute a 100MB sql file to recreate a db, i have done this like hundred times earlier and it works fine, takes like 5 mins but works, have tried on diff machines.
but on one machine i consisantly get bal allocation error, can you help?
system has 2 GB of ram, other succesfule systems also had same config.

How to repeat:
Try and execute a big sql file(around 100MB) that will create multiple tables and few tables having millions of records, you will get bad allocation error.

Please, check if upgrade to 5.2.37 helps. If it does not, please, send the output of Help > System Info.

Thank you for the report.

Problem with same file on single machine looks like problem is in machine, not in MySQL. So this looks like not MySQL bug, rather support request. This bug database is intended for discussion on MySQL bugs only.

Support on using our products is available both free in our forums at http://forums.mysql.com/ and for a reasonable fee direct from our skilled support engineers at http://www.mysql.com/support/

If you still think problem is MySQL code we need repeatable test case from you: problem file, name of MySQL package you downloaded (version 5.2.35 looks like nonsence for me: we have no server package of such a version), configuration file and repeatable instructions of how do you load this SQL file (e.g. copy-paste of command string).

@Sveta:
"5.2.35" obviously refers to Workbench version - not MySQL server version.  Also when this reporter writes "MySQL" he means "MySQL Workbench".

There are more reprots of WB failures with import from large files.

Peter
(not a MySQL person)

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