Bug #65472 "bad allocation" while importing 16.000 INSERT SQL
Submitted: 31 May 2012 13:35 Modified: 30 Jun 2012 14:55
Reporter: Martin Rudel Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Workbench: SQL Editor Severity:S1 (Critical)
Version:5.2.40 OS:Windows (Microsoft Windows 7 Service Pack 1 (build 7601), 64-bit)
Assigned to: CPU Architecture:Any
Tags: WBBugReporter

[31 May 2012 13:35] Martin Rudel 
Description:
 MySQL Workbench crashed with error msg "Bad allocation" on a Win 7 64bit Laptop with 4GB. 

How to repeat:
After a select creating about 16.000 rows with lesser columns from 560.000 rows with more columns, I exported the dataset into INSERT sql statements. While trying to import them into new table with lesser columns with identical column attributes, CRASH
[31 May 2012 14:55] Valeriy Kravchuk 
How large is the .sql file with INSERT statements?
[1 Jul 2012 1:00] Bugs System 
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".