Bug #2575 Mysql 4.0.17 crashes frequently on windows
Submitted: 30 Jan 2004 0:19 Modified: 29 Feb 2004 7:34
Reporter: Brendan Fernandes Email Updates:
Status: No Feedback Impact on me:
Category:MySQL Server Severity:S2 (Serious)
Version:4.0.17 OS:Windows (Windows Server 2003 Standard)
Assigned to: CPU Architecture:Any

[30 Jan 2004 0:19] Brendan Fernandes
I run a website with fairly moderate load; a total of 1gb of data, 2000-7000 hits per day.

Around 5 times a day, the server crashes. If using mysqld-max-nt, I see the following entry in the Windows event log:

Faulting application mysqld-max-nt.exe, version, faulting module mysqld-max-nt.exe, version, fault address 0x000c876e.

The address is consistent. If using mysqld-nt, I see the following entry in the event log. Again, the address is consistent:

Faulting application mysqld-nt.exe, version, faulting module mysqld-nt.exe, version, fault address 0x000c47fe.

The site is running under Apache Tomcat (have used versions 4.1 and 5.0), connecting via mysql/connectorJ (have tried versions 2 and 3).

All tables are MyIsam.

How to repeat:
There is nothing specific that causes this to happen. Generally, there is no particular query that seems to crash the server, though it seems to crash under heavy load.

It sometimes happens during a mysqldump of the database.

I have tried various settings for query_cache_size (including 0).

Other notable settings in my.ini:

If you need any help with trying to repeat this, please do not hesitate to contact me.
[30 Jan 2004 0:23] Brendan Fernandes
More useful information:

I was running the site, with the same database fine under Red Hat Linux with mysql version 3.23.41.
I had to change to a Windows server for various reasons, and retrieved the latest production version of mysql to run it on.

I started with 4.0.14, which was the latest release at the time. Mysql was crashing with the following entry in the Event log:

Faulting application mysqld-max-nt.exe, version, faulting module mysqld-max-nt.exe, version, fault address 0x000c749e.

Hope this helps,
[31 Jan 2004 7:34] MySQL Verification Team
Thank you for writting this report.

This bug report forum is only for repeatable bug reports. For bug
reports like this one you should use the MySQL mailing list or buy
commercial support from MySQL AB.  

What we need is fully repeatable test case.

This test case should consist of the series of SQL commands or actaions that will always lead to the problem, in your case to the crash.
[14 Feb 2005 22:54] Bugs System
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".
[3 Jun 2008 20:42] Jonatas Cruz
I am still facing that exactly problem.