MySQL Bugs: #68563: InnoDB: The InnoDB memory heap is disabled

Bug #68563	InnoDB: The InnoDB memory heap is disabled
Submitted:	4 Mar 2013 16:20	Modified:	15 Apr 2013 12:04
Reporter:	Chris Walsh	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Server: Installing	Severity:	S3 (Non-critical)
Version:	5.6.10	OS:	Windows (Windows Server 2003)
Assigned to:		CPU Architecture:	Any

Description:
2013-03-04 11:22:30 28276 [Warning] Buffered warning: Performance schema disabled (reason: init failed).

2013-03-04 11:22:30 28276 [Note] Plugin 'FEDERATED' is disabled.
2013-03-04 11:22:30 28276 [Warning] option 'innodb-autoextend-increment': unsigned value 67108864 adjusted to 1000
2013-03-04 11:22:30 91c 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.
2013-03-04 11:22:30 28276 [Note] InnoDB: The InnoDB memory heap is disabled
2013-03-04 11:22:30 28276 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-03-04 11:22:30 28276 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-03-04 11:22:30 28276 [Note] InnoDB: CPU does not support crc32 instructions
2013-03-04 11:22:30 91c  InnoDB: Assertion failure in thread 2332 in file ut0mem.cc line 105
InnoDB: Failing assertion: ret || !assert_on_error
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.

How to repeat:
Happens when installing 5.6.10 Mysql for Windows on server running Windows 2003 Server

Thank you for the report.

Please send us your configuration file.

my.ini

Attachment: my.ini (application/octet-stream, text), 13.92 KiB.

mysql-server-5.6-win32:6 - Looking for valid template
mysql-server-5.6-win32:12 - Found valid template.
mysql-server-5.6-win32:18 - Attempting to process template.
mysql-server-5.6-win32:25 - Processed template.
mysql-server-5.6-win32:31 - Attempting to configure service.
mysql-server-5.6-win32:37 - Configured service.
mysql-server-5.6-win32:43 - Attempting to start service.
mysql-server-5.6-win32:100 - Unable to configure service.
mysql-server-5.6-win32:100 - Product configuration controller finished configuration.

Hi, I am wondering if you could help find a solution? Thanks

Your my.ini is invalid. There are multiple wrong values there. Did installer create this?  I'd suggest you simply use this my.ini instead:

----
[client]
no-beep
port=3306

[mysql]
default-character-set=utf8

[mysqld]
port=3306
basedir="C:\Program Files\MySQL\MySQL Server 5.6\"
datadir="C:\Documents and Settings\All Users\Application Data\MySQL\MySQL Server 5.6\data\"
character-set-server=utf8
default-storage-engine=INNODB
sql-mode="STRICT_TRANS_TABLES,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION"
log-error="NAS.err"
max_connections=100
query_cache_size=0
query_cache_type=0
table_open_cache=2000
innodb_buffer_pool_size=256M
innodb_log_file_size=48M
innodb_concurrency_tickets=5000
innodb_stats_on_metadata=0
innodb_file_per_table=1
flush_time=0
----

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