MySQL Bugs: #76667: Unable to start the mysql server

Bug #76667	Unable to start the mysql server
Submitted:	12 Apr 2015 16:37	Modified:	15 Mar 2018 23:44
Reporter:	darshan danpal	Email Updates:
Status:	Can't repeat	Impact on me:	None
Category:	MySQL Server: Errors	Severity:	S1 (Critical)
Version:	6.2.4	OS:	Windows (Microsoft Windows 8.1 Single Language)
Assigned to:		CPU Architecture:	Any
Tags:	WBBugReporter

Description:
2015-04-12 22:01:16 - Workbench will use cmd shell commands to start/stop this instance
2015-04-12 22:01:18 - Starting server...
2015-04-12 22:01:23 - Server start done.

FROM DARSHAN-PC.err:
    2015-04-12 22:01:21  14016  Note  Plugin 'FEDERATED' is disabled.
          2015-04-12 22:01:21 1b94 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.
    2015-04-12 22:01:21  14016  Note  InnoDB: Using atomics to ref count buffer pool pages
    2015-04-12 22:01:21  14016  Note  InnoDB: The InnoDB memory heap is disabled
    2015-04-12 22:01:21  14016  Note  InnoDB: Mutexes and rw_locks use Windows interlocked functions
    2015-04-12 22:01:21  14016  Note  InnoDB: Memory barrier is not used
    2015-04-12 22:01:21  14016  Note  InnoDB: Compressed tables use zlib 1.2.3
    2015-04-12 22:01:21  14016  Note  InnoDB: Not using CPU crc32 instructions
    2015-04-12 22:01:21  14016  Note  InnoDB: Initializing buffer pool, size = 142.0M
    2015-04-12 22:01:21  14016  Note  InnoDB: Completed initialization of buffer pool
    2015-04-12 22:01:21  14016  Note  InnoDB: Highest supported file format is Barracuda.
    2015-04-12 22:01:21  14016  Note  InnoDB: 128 rollback segment(s) are active.
    2015-04-12 22:01:21  14016  Note  InnoDB: Waiting for purge to start
          InnoDB: Error: tablespace id is 46 in the data dictionary
          InnoDB: but in file .\mydb\leeds.ibd it is 45!
          2015-04-12 22:01:21 ebc  InnoDB: Assertion failure in thread 3772 in file fil0fil.cc line 796
          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.
2015-04-12 22:01:24 - Checking server status...
2015-04-12 22:01:24 - Trying to connect to MySQL...
2015-04-12 22:01:24 - Can't connect to MySQL server on '127.0.0.1' (10061) (2003)
2015-04-12 22:01:24 - Assuming server is not running
2015-04-12 22:01:24 - Checking server status...
2015-04-12 22:01:24 - Trying to connect to MySQL...
2015-04-12 22:01:24 - Can't connect to MySQL server on '127.0.0.1' (10061) (2003)
2015-04-12 22:01:24 - Assuming server is not running

How to repeat:
It is occurring in my local pc.., not sure how u can reproduce this error

Have you touch the InnoDB files copy/paste/delete etc?. Thanks.

Thanks Miguel.

No.. I have not touch any InnoDB, Is there any chance malware or any other virus has manipulated the files..
And also what is the other possibility to occur this error and what will be the fix.

I wasn't able to repeat this issue with the info provided.

I wasn't able to repeat this issue with the info provided.