MySQL Bugs: #66078: Use navicat to copy table,mysql crashed on windows 2003

Bug #66078	Use navicat to copy table,mysql crashed on windows 2003
Submitted:	30 Jul 2012 2:40	Modified:	28 Feb 2013 17:34
Reporter:	darkz hei	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Server	Severity:	S3 (Non-critical)
Version:	5.6.6-labs-june-2012-log	OS:	Windows (windows 2003 with sp2 32 bit)
Assigned to:		CPU Architecture:	Any
Tags:	copy table, navicat

Description:
When I use navicat to connect to the mysql 5.6.6-labs-june-2012-log downloaded from labs.mysql.com, open a database,and use ctrl+c ,ctrl+v to copy a table,the client navicate told me that lost connect from the mysql server.

Nothing write in the error log,and the service in windows service tools is stop,when I restart the mysql service,the copy result table show in the navicate...

How to repeat:
use mysql 5.6.6-labs-june-2012-log and the navicate 8.2.12-enterprise,in the navicate ,use ctrl+c on the select table and ctrl+v to paste it ,then it told that the mysql server lost connect.

I saw that the engine of the table to copy is innodb by default...

Is there anything related in Even Viewer logs at OS level? Is it possible for you to repeat this crash with general query log enabled?

what in the windows 2003 syslog says:
错误应用程序 mysqld.exe，版本 5.6.6.0，错误模块 ntdll.dll，版本 5.2.3790.4937，错误地址 0x0004cd12。

Application Error:application error:mysqld.exe version 5.6.6.0 module:ntdll.dll,version:5.2.3790.4937,address 0x0004cd12.

DrWatson：
应用程序 D:\MySQL\bin\mysqld.exe 产生了一个应用程序错误 此错误发生在 07/30/2012 @ 17:53:00.964 所产生的意外情况为 c0000005，在地址 7C97CD12 (ntdll!RtlIpv4StringToAddressExW)处

application error:D:\MySQL\bin\mysqld.exe occour an error 07/30/2012 @ 17:53:00.964 code:c0000005,address 7C97CD12 (ntdll!RtlIpv4StringToAddressExW)

Thank you for the report.

Have you run mysql_upgrade after installing version 5.6.6? Please also turn general query log to ON, repeat same error with Navicat and send us general query log content: I hope last query in the general query log would be one which causes the issue.

what I saw is that ,the memusage of mysqld is to large:
when the service start:
mysqld.exe mem:875.040K,swap:1,414,620K
when copy the table:
mysqld.exe mem:1,424,600K,swap:1,426,204K

My server is cpu:E5200,ram:2G,swap:system control.

when I copy the table,the cpu usage is rush to be hight from less than 10% to over 40%.

what says in the general query log is:
--------------------------------------------------------------------------------------------
D:\MySQL\bin\mysqld, Version: 5.6.6-labs-june-2012-log (MySQL Community Server (GPL)). started with:
TCP Port: 3306, Named Pipe: D:/MySQL/mysql.sock
Time                 Id Command    Argument
120809 16:26:21	    3 Query	show global variables like '%log%'
120809 16:26:31	    4 Connect	root@127.0.0.1 on 
		    4 Query	SET NAMES 'utf8'
		    4 Query	SHOW VARIABLES LIKE 'lower_case_%'
		    4 Query	SHOW VARIABLES LIKE 'profiling'
		    4 Query	SHOW CHARACTER SET
		    4 Query	SHOW COLLATION
		    4 Query	SHOW DATABASES
		    5 Connect	root@127.0.0.1 on 
		    5 Query	SET NAMES 'utf8'
		    5 Init DB	test
		    5 Query	SELECT @@character_set_database, @@collation_database
		    5 Query	SHOW FULL TABLES WHERE Table_type != 'VIEW'
		    5 Query	SHOW FULL TABLES WHERE Table_type = 'VIEW'
		    5 Query	SHOW PROCEDURE STATUS
		    5 Query	SHOW FUNCTION STATUS
		    5 Query	SELECT EVENT_CATALOG, EVENT_SCHEMA, EVENT_NAME, DEFINER, EVENT_DEFINITION, EVENT_TYPE, SQL_MODE, STATUS, EXECUTE_AT, INTERVAL_VALUE, INTERVAL_FIELD, STARTS, ENDS, ON_COMPLETION, CREATED, LAST_ALTERED, LAST_EXECUTED, EVENT_COMMENT FROM information_schema.EVENTS WHERE EVENT_SCHEMA='test'ORDER BY EVENT_NAME
		    5 Query	SHOW FULL TABLES WHERE Table_type != 'VIEW'
		    5 Query	SHOW FULL TABLES WHERE Table_type = 'VIEW'
		    5 Query	SHOW CREATE TABLE `a_copy1_copy`
		    5 Query	SET SESSION foreign_key_checks=0
		    5 Query	CREATE TABLE `a_copy1_copy_copy`(
  `id` int(11) DEFAULT NULL,
  `name` varchar(10) DEFAULT NULL
) ENGINE=InnoDB DEFAULT CHARSET=utf8
		    5 Query	INSERT INTO `a_copy1_copy_copy` SELECT * FROM `test`.`a_copy1_copy`
--------------------------------------------------------------------------------------------

Thank you for the feedback.

Last query is "INSERT INTO `a_copy1_copy_copy` SELECT * FROM `test`.`a_copy1_copy`
"

How many rows in table a_copy1_copy? Please send output of SHOW CREATE TABLE a_copy1_copy and SHOW TABLE STATUS LIKE 'a_copy1_copy'

The original table is table a,the copied table is a_copy,a_copy is not exists before copied from table a,and table a only has 14 rows...
blow is what you want to know:
mysql> show create table a;
+-------+---------------------------------------------------------------------------------------------------------------------+
| Table | Create Table                                                                                                        |
+-------+---------------------------------------------------------------------------------------------------------------------+
| a     | CREATE TABLE `a` (
  `id` int(11) DEFAULT NULL,
  `name` varchar(10) DEFAULT NULL
) ENGINE=InnoDB DEFAULT CHARSET=utf8 |
+-------+---------------------------------------------------------------------------------------------------------------------+
1 row in set

mysql> SHOW TABLE STATUS LIKE 'a_copy';
+--------+--------+---------+------------+------+----------------+-------------+-----------------+--------------+-----------+----------------+---------------------+-------------+------------+-----------------+----------+----------------+---------+
| Name   | Engine | Version | Row_format | Rows | Avg_row_length | Data_length | Max_data_length | Index_length | Data_free | Auto_increment | Create_time         | Update_time | Check_time | Collation       | Checksum | Create_options | Comment |
+--------+--------+---------+------------+------+----------------+-------------+-----------------+--------------+-----------+----------------+---------------------+-------------+------------+-----------------+----------+----------------+---------+
| a_copy | InnoDB |      10 | Compact    |   14 |           1170 |       16384 |               0 |            0 |         0 | NULL           | 2012-07-30 10:17:37 | NULL        | NULL       | utf8_general_ci | NULL     |                |         |
+--------+--------+---------+------------+------+----------------+-------------+-----------------+--------------+-----------+----------------+---------------------+-------------+------------+-----------------+----------+----------------+---------+
1 row in set

Thank you for the feedback.

I was not able to repeat this issue. Please try in your environment with version 5.6.9rc and inform us if problem still exists.

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