MySQL Bugs: #91076: InnoDB: Unable to allocate memory of size

Bug #91076	InnoDB: Unable to allocate memory of size
Submitted:	30 May 2018 12:30	Modified:	6 Jun 2018 17:02
Reporter:	Dipu Mathew	Email Updates:
Status:	Not a Bug	Impact on me:	None
Category:	MySQL Server: InnoDB storage engine	Severity:	S2 (Serious)
Version:	5.6.39	OS:	Windows
Assigned to:	MySQL Verification Team	CPU Architecture:	Other (X64)
Tags:	InnoDB: Unable to allocate memory of size

Description:
The config for innodb_buffer_pool_size=24G and the server have 32GB of physical RAM . 

018-05-29 23:23:15 10316 [ERROR] C:\Program Files\MySQL\MySQL Server 5.6\bin\mysqld.exe: Out of memory (Needed 2199776 bytes)
2018-05-29 23:23:23 10316 [ERROR] InnoDB:  InnoDB: Unable to allocate memory of size 1065064.

2018-05-29 23:23:23 c5b4  InnoDB: Assertion failure in thread 50612 in file ha_innodb.cc line 17381
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.6/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
2018-05-29 23:23:26 10316 [ERROR] Can't create thread to handle request (errno= 22)
2018-05-29 23:23:28 10316 [ERROR] InnoDB:  InnoDB: Unable to allocate memory of size 1065064.

2018-05-29 23:23:28 c634  InnoDB: Assertion failure in thread 50740 in file ha_innodb.cc line 17381
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.6/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
2018-05-30 00:33:45 23108 [Note] Plugin 'FEDERATED' is disabled.
2018-05-30 00:33:45 3358 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2018-05-30 00:33:45 23108 [Note] InnoDB: Using atomics to ref count buffer pool pages
2018-05-30 00:33:45 23108 [Note] InnoDB: The InnoDB memory heap is disabled
2018-05-30 00:33:45 23108 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2018-05-30 00:33:45 23108 [Note] InnoDB: Memory barrier is not used
2018-05-30 00:33:45 23108 [Note] InnoDB: Compressed tables use zlib 1.2.3
2018-05-30 00:33:45 23108 [Note] InnoDB: Not using CPU crc32 instructions
2018-05-30 00:33:45 23108 [Note] InnoDB: Initializing buffer pool, size = 24.0G
2018-05-30 00:33:48 23108 [Note] InnoDB: Completed initialization of buffer pool
2018-05-30 00:33:49 23108 [Note] InnoDB: Highest supported file format is Barracuda.
2018-05-30 00:33:49 23108 [Note] InnoDB: Log scan progressed past the checkpoint lsn 5665550940631
2018-05-30 00:33:49 23108 [Note] InnoDB: Database was not shutdown normally!
2018-05-30 00:33:49 23108 [Note] InnoDB: Starting crash recovery.
2018-05-30 00:33:49 23108 [Note] InnoDB: Reading tablespace information from the .ibd files...
2018-05-30 00:33:52 23108 [Note] InnoDB: Restoring possible half-written data pages 
2018-05-30 00:33:52 23108 [Note] InnoDB: from the doublewrite buffer...
InnoDB: Doing recovery: scanned up to log sequence number 5665556183040
InnoDB: Doing recovery: scanned up to log sequence number 5665561425920
InnoDB: Doing recovery: scanned up to log sequence number 5665566668800
InnoDB: Doing recovery: scanned up to log sequence number 5665571911680
InnoDB: Doing recovery: scanned up to log sequence number 5665577154560
InnoDB: Doing recovery: scanned up to log sequence number 5665582397440

How to repeat:
The same database crash happened twice before and it is happening random time .

Hi,
This is not a bug but missconfiguration of the server. Our MySQL Support team will be happy to help you properly configure your sever.

Best regards
Bogdan

I have the same issue as well. How was this issue fixed? What can I do to fix this issue. I have the following below errors.
Timestamp, Thread, Type, Details
2018-12-10 01:13:38, 19228, ERROR, InnoDB:  InnoDB: Unable to allocate memory of size 1065016.

I have the same issue. How was this issue fixed? what can i do to fix this issue?

Affects me in MySQL 5.6.51

2022-05-09 15:35:03 7f5746fbb700  InnoDB: Assertion failure in thread 140012829783808 in file ha_innodb.cc line 18752
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.6/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
15:35:03 UTC - mysqld got signal 6 ;

Hi. Did you find out what was the reason for this issue? After running fine for 12 days, this started happening on one of our MySQL 8.4-instances. Would appreciate some pinpoints on how to solve this.

Espen Corneliussen,  please open a new bug report and upload full mysql error log.  5.6 cannot really compare to 8.4,  they're too different.