Description:
This DB Server used in conjunction with DBMoto replication service between MS-SQL server at remote site and our local MySQL DB server pair (Primary & replica/backup servers). This trap occurred shortly after replica server re-established connection proceeding weekly backup process on replica. The DBMoto service on another workstation establishes multiple connections for replication of log events from MS-SQL server. Log appears below:
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 852cbb491f46d0fc852cdd5ff53bd0fc852cffd49af1cffc852c21bb4099cffc852c33f19e4ed0fc852c55e756d139f9852c77fdad7f3af9852c994311e0cffc852cabf92e16d0fc852cccebf8c4cefc852cee59edbacefc852c1087ad6fcefc852c22a53227d0fc852c8453d7d4fc788c2ca6d1c582fd788c2cc8ef589f32788c2cda4d79cd32788c2cfbaa7fc732788c2c1de96f10fd788c2c3fa753a332788c2c51a5f17afd788c2c73731662fc788c2c95f1c50632788c2cb76fcc7cfd788c2cca9c422433788c2cecae961d33788c2c0ef8bd4f33788c2c300ae43932788c2c4204c26c32788c2c64767aaf06798c2c86004fe206798c2c0008000000000000000000000000000000000000000000009268a5200000000072306375722e63002a0600000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000700400000000000000000000000000000000000000000000f0000000000000007000000000000000000000000000000010000000000000000d00000000000000070000800000000008000000000000000c0000000000000010000000000000001100000000000000150000000000000016000000000000001c00000000000000230000000000000027000000000000002b000000000000002b000080000000002b00; asc …,»I FÐü…,Ý_õ;Ðü…,ÿÔšñÏü…,!»@ Ïü…,3ñžNÐü…,UçVÑ9ù…,wý :ù…, C àÏü…,«ù. Ðü…,ÌëøÄÎü…,îYíºÎü…, ‡oÎü…,"¥2'Ðü…,„S×ÔüxŒ,¦ÑÅ‚ýxŒ,ÈïXŸ2xŒ,ÚMyÍ2xŒ,ûª Ç2xŒ, éo ýxŒ,?§S£2xŒ,Q¥ñzýxŒ,ss büxŒ,•ñÅ 2xŒ,·oÌ|ýxŒ,ÊœB$3xŒ,ì®– 3xŒ, ø½O3xŒ,0 ä92xŒ,B Âl2xŒ,dvz¯ yŒ,† Oâ yŒ, ’h¥ r0cur.c * p ð p # ' + + + ;
InnoDB: Scanning backward trying to find previous allocated mem blocks
Mem block at - 2024, file w0ins.c, line 306
Freed mem block at - 2536, file r0cur.c, line 2870
Freed mem block at - 3048, file 0undo.c, line 1394
Freed mem block at - 3304, file m0rec.c, line 1247
Freed mem block at - 3560, file m0rec.c, line 1247
Mem block at - 4072, file 0undo.c, line 1394
Freed mem block at - 5096, file purge.c, line 49
Mem block at - 6120, file w0ins.c, line 82
Mem block at - 7144, file mysql.c, line 591
Mem block at - 8168, file w0ins.c, line 82
InnoDB: Scanning forward trying to find next allocated mem blocks
Freed mem block at + 24, file r0cur.c, line 1578
Freed mem block at + 536, file e0cur.c, line 934
Freed mem block at + 1048, file r0sea.c, line 1169
Freed mem block at + 2072, file purge.c, line 339
Freed mem block at + 4632, file 0pcur.c, line 29
Freed mem block at + 5144, file mysql.c, line 591
Freed mem block at + 6168, file r0sea.c, line 1169
Freed mem block at + 9240, file 0pcur.c, line 29
Freed mem block at + 10264, file 0pcur.c, line 29
Freed mem block at + 10776, file nodb.cc, line 3111
080208 6:36:38 InnoDB: Assertion failure in thread 3804 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.
InnoDB: Thread 3180 stopped in file C:\cygwin\home\mysqldev\build\mysql-5.1.22-rc-winbuild\mysql-community-nt-5.1.22-rc-build\storage\innobase\include\sync0sync.ic line 115
InnoDB: Thread 3172 stopped in file .\os\os0sync.c line 489
InnoDB: Thread 3176 stopped in file C:\cygwin\home\mysqldev\build\mysql-5.1.22-rc-winbuild\mysql-community-nt-5.1.22-rc-build\storage\innobase\include\sync0sync.ic line 115
InnoDB: Thread 3176 stopped in file C:\cygwin\home\mysqldev\build\mysql-5.1.22-rc-winbuild\mysql-community-nt-5.1.22-rc-build\storage\innobase\include\sync0sync.ic line 115
InnoDB: Thread 3180 stopped in file C:\cygwin\home\mysqldev\build\mysql-5.1.22-rc-winbuild\mysql-community-nt-5.1.22-rc-build\storage\innobase\include\sync0rw.ic line 364
InnoDB: Thread 3172 stopped in file .\os\o
How to repeat:
Not sure how to recreate. No actual human driven sessions where active at this time.
