Bug #1887 InnoDb data recovery
Submitted: 19 Nov 2003 4:42 Modified: 27 Jan 2004 10:36
Reporter: [ name withheld ] Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: InnoDB storage engine Severity:S1 (Critical)
Version:4.1 alpha OS:Windows (Windows XP)
Assigned to: CPU Architecture:Any

[19 Nov 2003 4:42] [ name withheld ] 
Description:
  I am facing a problem in starting my MySQL database.It was working fine, but one day it did not start.
Following are my configurations.
516 RAM
Windows XP
phptriad
Mysql4.1 alpha
I am using InnoDB database type.

Follwing the error logged in mysql.err file:
031119 17:53:09  InnoDB: Fatal error: cannot allocate 4294961632 bytes of
InnoDB: memory with malloc! Total allocated memory
InnoDB: by InnoDB 209667231 bytes. Operating system errno: 8
InnoDB: Cannot continue operation!
InnoDB: Check if you should increase the swap file or
InnoDB: ulimits of your operating system.
InnoDB: On FreeBSD check you have compiled the OS with
InnoDB: a big enough maximum process size.
InnoDB: We now intentionally generate a seg fault so that
InnoDB: on Linux we get a stack trace.

How to repeat:
We can send the ibdata1 file if required.
[4 Dec 2003 6:27] Alexander Keremidarski 
Sorry, but the bug system is not the appropriate forum for asking
support questions. Your problem is not the result of a bug.
For a list of more appropriate places to ask for help using MySQL
products, please visit http://www.mysql.com/support/

Thank you for your interest in MySQL.

Error message is quite clear I believe:

516 RAM
.err file:
031119 17:53:09  InnoDB: Fatal error: cannot allocate 4294961632 bytes of
InnoDB: memory with malloc! Total allocated memory
InnoDB: by InnoDB 209667231 bytes. Operating system errno: 8

4294961632 = 4Gb
209667231 = 2Gb
[4 Dec 2003 7:12] Heikki Tuuri 
Hi!

4.1.0 is very old. Best to wait for 4.1.1 to be released.

We need more information, especially your my.cnf or my.ini file, if the problem still appears.

Best regards,

Heikki
[27 Jan 2004 10:36] Heikki Tuuri 
Hi!

I am closing this bug report, because there has been no feedback after 4.1.1 was released.

Regards,

Heikki