handler.cc int handler::ha_write_row(uchar *buf) { int error; Log_func *log_func= Write_rows_log_event::binlog_row_logging_function; DBUG_ENTER("handler::ha_write_row"); mark_trx_read_write(); if (unlikely(error= write_row(buf))) <<<<<<<<<<<<<<<5.1\bin\mysqld --standalone --console 080430 20:10:54 InnoDB: Started; log sequence number 0 46409 080430 20:10:55 [Note] Event Scheduler: Loaded 0 events 080430 20:10:55 [Note] 5.1\bin\mysqld: ready for connections. Version: '5.1.25-rc-nt' socket: '' port: 3306 Source distribution InnoDB: Error: Memory area size 2048, next area size 0 not a power of 2! InnoDB: Possibly a memory overrun of the buffer being freed here. InnoDB: Apparent memory corruption: mem dump len 500; hex 000000000000000000000000000000000000040000000000000018c9c5020000000004000000000000000 0000000000000020c9c502000000000400000000000000040000000000000028c9c502000000000400000000000000040000000000000030c9c50200000000040000000000000004 00000000000000000000000000000070000000000000004000000000000000500008000000000040000000000000008000000000000000c000000000000001000000000000000a61 8ba42d3b9cefc64e15074bdb70efc34732c6bcea01f16e93b89b687e01f1837fbef048d001f1253768c6ddcb01f1ff92ac5fc8a301f1c6669b9a45ba01f100080000000000000000 0000000000000000000000000009268a5200000000074306d656d2e63002f0000000000000000000000000000000000000000000000000000000000000078d0c5020000000000000 0000000000b00400000000000000000000000000000000000000000000f0000000000000007000000000000000000000000000000006030500040000000603050004002000060305 004004000060305000400600005000000000000000900000000000000220000000000000026000000000000002a000000000000002e0000000000000032000000000000000000000 00000000000000000000000000000000000000000000; asc ÉÅ ÉÅ (ÉÅ 0ÉÅ ¦ <¤-;oïÆN KÛpïÃG2Ƽê ñn"¸>h~ ñƒ ¾ðHÐ ñ%7hÆÝË ñÿ'¬_È ñÆf>sEº ñ 'h¥ t0mem.c / xÐÅ ° ð p @ ` " & * . 2 ; InnoDB: Scanning backward trying to find previous allocated mem blocks Freed mem block at - 1000, file t0mem.c, line 246 Freed mem block at - 4072, file 0ibuf.c, line 3140 Freed mem block at - 4584, file 0pcur.c, line 286 Freed mem block at - 5096, file n0dyn.c, line 33 Freed mem block at - 6120, file e0cur.c, line 934 Mem block at - 8168, file 0roll.c, line 611 Mem block at - 16360, file mysql.c, line 597 Mem block at - 20456, file mysql.c, line 597 Mem block at - 21480, file t0mem.c, line 246 Mem block at - 22504, file nodb.cc, line 3127 InnoDB: Scanning forward trying to find next allocated mem blocks Freed mem block at + 24, file t0mem.c, line 47 Freed mem block at + 280, file t0mem.c, line 246 Freed mem block at + 536, file r0btr.c, line 569 Freed mem block at + 1048, file t0mem.c, line 47 Freed mem block at + 2072, file t0mem.c, line 47 Freed mem block at + 2328, file t0mem.c, line 246 Freed mem block at + 2584, file e0cur.c, line 934 Mem block at + 3096, file 0ibuf.c, line 1318 Mem block at + 4120, file t0mem.c, line 47 Freed mem block at + 5144, file t0mem.c, line 47 080430 20:48:12 InnoDB: Assertion failure in thread 1792 in file .\mem\mem0pool.c line 518 InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to http://bugs.mysql.com. InnoDB: If you get repeated assertion failures or crashes, even InnoDB: immediately after the mysqld startup, there may be InnoDB: corruption in the InnoDB tablespace. Please refer to InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html InnoDB: about forcing recovery. 080430 20:48:13 - mysqld got exception 0xc0000005 ; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. key_buffer_size=8388600 read_buffer_size=131072 max_used_connections=2 max_threads=151 threads_connected=2 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 338097 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. thd: 0x38d1400 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... InnoDB: Thread 5116 stopped in file C:\dbs\mysql-5.1\storage\innobase\include\sync0sync.ic line 115 InnoDB: Thread 2360 stopped in file C:\dbs\mysql-5.1\storage\innobase\include\sync0sync.ic line 115 0000000140371B20 mysqld.exe!mem_area_free() 000000014031EE50 mysqld.exe!mem_heap_free_func() 00000001403777A5 mysqld.exe!ibuf_page_low() 0000000140379022 mysqld.exe!ibuf_get_volume_buffered() 000000014037965D mysqld.exe!ibuf_update_max_tablespace_id() 0000000140379B9C mysqld.exe!ibuf_insert() 000000014034E2B1 mysqld.exe!btr_cur_search_to_nth_level() 00000001403934A2 mysqld.exe!row_ins_index_entry_low() 0000000140393EEE mysqld.exe!row_ins() 000000014039407C mysqld.exe!row_ins_step() 00000001403191E9 mysqld.exe!row_insert_for_mysql() 0000000140309720 mysqld.exe!?write_row@ha_innobase@@UEAAHPEAE@Z() 000000014002DF7C mysqld.exe!handler::ha_write_row()[handler.cc:4519] 0000000140154AF7 mysqld.exe!write_record()[sql_insert.cc:1557] 00000001401621C4 mysqld.exe!read_sep_field()[sql_load.cc:851] 0000000140162C24 mysqld.exe!mysql_load()[sql_load.cc:395] 000000014016E28F mysqld.exe!mysql_execute_command()[sql_parse.cc:3216] 0000000140171D5C mysqld.exe!mysql_parse()[sql_parse.cc:5634] 0000000140172893 mysqld.exe!dispatch_command()[sql_parse.cc:1123] 00000001401735D8 mysqld.exe!do_command()[sql_parse.cc:781] 0000000140209267 mysqld.exe!handle_one_connection()[sql_connect.cc:1115] 0000000140281B25 mysqld.exe!pthread_start() 00000001403CC0D7 mysqld.exe!_callthreadstart()[thread.c:295] 00000001403CC1A5 mysqld.exe!_threadstart()[thread.c:275] 00000000776DCDCD kernel32.dll!BaseThreadInitThunk() 000000007782C6E1 ntdll.dll!RtlUserThreadStart() Trying to get some variables. Some pointers may be invalid and cause the dump to abort... thd->query at 00000000038A6BA0=load data infile 'c:/temp/parts.tsv' into table imdb_development.parts character set 'Latin1' fields terminated by '\t' lines terminated by '\r\n' (movie_id, creditseq, person_id, role, part) thd->thread_id=6 thd->killed=NOT_KILLED The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains information that should help you find out what is causing the crash. c:\dbs>5.1\bin\mysqld --standalone --console InnoDB: Log scan progressed past the checkpoint lsn 0 92450101 080430 20:56:10 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... 080430 20:56:11 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 4 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 InnoDB: Apply batch completed 080430 20:56:12 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 4 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 InnoDB: Apply batch completed 080430 20:56:14 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 4 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 InnoDB: Apply batch completed 080430 20:56:17 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 4 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 InnoDB: Apply batch completed InnoDB: Doing recovery: scanned up to log sequence number 0 97692672 InnoDB: Doing recovery: scanned up to log sequence number 0 98285133 InnoDB: 1 transaction(s) which must be rolled back or cleaned up InnoDB: in total 215551 row operations to undo InnoDB: Trx id counter is 0 1792 080430 20:56:19 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 0 1 2 InnoDB: Error: Memory area size 2048, next area size 0 not a power of 2! InnoDB: Possibly a memory overrun of the buffer being freed here. InnoDB: Apparent memory corruption: mem dump len 500; hex 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000080000000000000000 0000000000000000000000000009268a5200000000074306d656d2e63002f0000000000000000000000000000000000000000000000000000000000000078f43a030000000000000 0000000000b00400000000000000000000000000000000000000000000d80000000000000070000000000000000000000000000000e8e83a03000000000000000000000000001000 004004000f0e83a03000000000000000000000000001000000600a000f8e83a0300003 000000004 005 000000000000106 107 000004004000e93a03000000000000000000000 000010000000000000000000000000000000000000000000000000; asc 8 'h¥ t0mem.c / xô: ° Ø p èè: @ ðè: 9 10   øè: @ é: ; InnoDB: Scanning backward trying to find previous allocated mem blocks Mem block at - 1000, file t0mem.c, line 47 Freed mem block at - 1256, file t0mem.c, line 47 Freed mem block at - 1512, file 0page.c, line 385 Freed mem block at - 1768, file t0mem.c, line 47 Mem block at - 2024, file t0mem.c, line 47 11 Freed mem block at - 4072, file t0mem.c, line 47 Mem block at - 6120, file purge.c, line 177 Freed mem block at - 7144, file t0mem.c, line 47 Mem block at - 8168, file purge.c, line 177 12 Mem block at - 10216, file x0trx.c, line 107 InnoDB: Scanning forward trying to find next allocated mem blocks Freed mem block at + 24, file t0mem.c, line 47 13 Freed mem block at + 2072, file t0mem.c, line 246 Freed mem block at + 3096, file t0mem.c, line 246 Freed mem block at + 4120, file t0mem.c, line 246 Freed mem block at + 6168, file t0mem.c, line 246 14 Freed mem block at + 8216, file t0mem.c, line 246 15 Freed mem block at + 10264, file t0mem.c, line 246 16 Freed mem block at + 12312, file t0mem.c, line 246 17 Freed mem block at + 18456, file t0mem.c, line 246 Freed mem block at + 20504, file t0mem.c, line 246 080430 20:56:19 InnoDB: Assertion failure in thread 1900 in file .\mem\mem0pool.c line 518 InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to http://bugs.mysql.com. InnoDB: If you get repeated assertion failures or crashes, even InnoDB: immediately after the mysqld startup, there may be InnoDB: corruption in the InnoDB tablespace. Please refer to InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html InnoDB: about forcing recovery. 18 19 InnoDB: Thread 4376 stopped in file C:\dbs\mysql-5.1\storage\innobase\include\sync0sync.ic line 115 InnoDB: Thread 1052 stopped in file C:\dbs\mysql-5.1\storage\innobase\include\sync0sync.ic line 115 080430 20:56:19 - mysqld got exception 0xc0000005 ; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. key_buffer_size=8388600 read_buffer_size=131072 max_used_connections=0 max_threads=151 threads_connected=0 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 338097 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. thd: 0x0 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... 0000000140371B20 mysqld.exe!mem_area_free() 000000014031EE50 mysqld.exe!mem_heap_free_func() 00000001403AC1E6 mysqld.exe!recv_scan_log_seg_for_backup() 00000001403ACAD1 mysqld.exe!recv_recover_page() 000000014036FE37 mysqld.exe!buf_page_io_complete() 0000000140365861 mysqld.exe!fil_aio_wait() 0000000140326358 mysqld.exe!srv_parse_log_group_home_dirs() 00000000776DCDCD kernel32.dll!BaseThreadInitThunk() 000000007782C6E1 ntdll.dll!RtlUserThreadStart() The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains information that should help you find out what is causing the crash. c:\dbs>5.1\bin\mysqld --standalone --console InnoDB: Log scan progressed past the checkpoint lsn 0 92450101 080430 20:57:18 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... 080430 20:57:19 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 4 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 InnoDB: Apply batch completed 080430 20:57:21 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 4 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 InnoDB: Apply batch completed 080430 20:57:22 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 4 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 InnoDB: Apply batch completed 080430 20:57:24 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 4 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 InnoDB: Apply batch completed InnoDB: Doing recovery: scanned up to log sequence number 0 97692672 InnoDB: Doing recovery: scanned up to log sequence number 0 98285133 InnoDB: 1 transaction(s) which must be rolled back or cleaned up InnoDB: in total 215551 row operations to undo InnoDB: Trx id counter is 0 1792 080430 20:57:25 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 4 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 InnoDB: Apply batch completed InnoDB: Starting in background the rollback of uncommitted transactions 080430 20:57:27 InnoDB: Started; log sequence number 0 98285133 080430 20:57:27 InnoDB: Rolling back trx with id 0 1284, 215551 rows to undo InnoDB: Progress in percents: 1080430 20:57:27 [Note] Event Scheduler: Loaded 0 events 080430 20:57:27 [Note] 5.1\bin\mysqld: ready for connections. Version: '5.1.25-rc-nt' socket: '' port: 3306 Source distribution 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 5 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 10 InnoDB: Rolling back of trx id 0 1284 completed 080430 21:06:32 InnoDB: Rollback of non-prepared transactions completed 080430 21:09:10 [Note] 5.1\bin\mysqld: Normal shutdown 080430 21:09:10 [Note] Event Scheduler: Purging the queue. 0 events 080430 21:09:12 [Warning] 5.1\bin\mysqld: Forcing close of thread 1 user: 'root' 080430 21:09:12 InnoDB: Starting shutdown... 080430 21:09:14 InnoDB: Shutdown completed; log sequence number 0 118357622 080430 21:09:14 [Note] 5.1\bin\mysqld: Shutdown complete c:\dbs>5.1\bin\mysqld --standalone --console 080430 21:09:29 InnoDB: Started; log sequence number 0 118357622 080430 21:09:29 [Note] Event Scheduler: Loaded 0 events 080430 21:09:29 [Note] 5.1\bin\mysqld: ready for connections. Version: '5.1.25-rc-nt' socket: '' port: 3306 Source distribution