MySQL Bugs: #69775: Windows Sevice Crash - InnoDB: Assertion failure in thread 2956 in file .\srv\sr

Bug #69775	Windows Sevice Crash - InnoDB: Assertion failure in thread 2956 in file .\srv\sr
Submitted:	18 Jul 2013 8:30	Modified:	11 Aug 2013 14:17
Reporter:	Ross Buggins	Email Updates:
Status:	Can't repeat	Impact on me:	None
Category:	MySQL Server: InnoDB storage engine	Severity:	S1 (Critical)
Version:	5.1.68	OS:	Windows (2012 Std)
Assigned to:		CPU Architecture:	Any
Tags:	crash

Description:
Windows Service Crash of MySql.exe.
10GB RAM, 6GB swap, 8GB innodb buffer pool.

InnoDB: ###### Diagnostic info printed to the standard error stream
InnoDB: Error: semaphore wait has lasted > 600 seconds
InnoDB: We intentionally crash the server, because it appears to be hung.
130717 20:15:36  InnoDB: Assertion failure in thread 2956 in file .\srv\srv0srv.c line 2275
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-innodb-recovery.html
InnoDB: about forcing recovery.
InnoDB: Thread 1484 stopped in file G:\mysql-5.1.68-winbuild\mysql-community-nt-5.1.68-build\storage\innobase\include\sync0sync.ic line 115
InnoDB: Thread 3080 stopped in file .\mem\mem0mem.c line 496
InnoDB: Thread 1476 stopped in file .\os\os0sync.c line 391
InnoDB: Thread 5280 stopped in file .\handler\ha_innodb.cc line 1431
InnoDB: Thread 4040 stopped in file G:\mysql-5.1.68-winbuild\mysql-community-nt-5.1.68-build\storage\innobase\include\sync0sync.ic line 115
130718  8:59:48 [Note] Plugin 'FEDERATED' is disabled.
130718  8:59:48  InnoDB: Initializing buffer pool, size = 8.0G
130718  8:59:48  InnoDB: Error: cannot allocate 4261429248 bytes of
InnoDB: memory with malloc! Total allocated memory
InnoDB: by InnoDB 23444152 bytes. Operating system errno: 8

How to repeat:
Unsure.

Thank you for the bug report. Is this machine dedicated only for MySQL Server? otherwise please try to decrease the InnoDB buffer pool. Thanks.

The first thing I did after the crash was to reduce the innodb buffer as I thought it would reduce the chance of it happening again. However, I don't believe the MySQL service should be crashing when memory is low.

we need the full error log from this server. the problem was not a crash, but a hang. innodb purposely killed mysqld-nt.exe after it appeared to hang too long.

note, 5.5.33 and 5.6.13 are the current version.  many bugs are fixed there, that may not be fixed in 5.1.68.  also, innodb plugin in 5.1 is probably better suited than builtin version.