MySQL Bugs: #13784: MySql crash

Bug #13784	MySql crash
Submitted:	5 Oct 2005 20:13	Modified:	5 Nov 2005 20:34
Reporter:	Constantin	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Server	Severity:	S1 (Critical)
Version:	5.0.7/5.0.13	OS:	Windows (win2003/Version 5.2.3790)
Assigned to:	MySQL Verification Team	CPU Architecture:	Any

Description:
Summary:
MySql server crashes
Port 3306 getting locked (Port 3306 getting locked (server has to be rebooted to acquire the port again)
One of the tables is corrupted

Attempt to fix the table repots access denied for roo@localhost to database information_schema.

System Info:
OS: Win2003 (Microsoft Windows [Version 5.2.3790])
It is a 2 cpu Xeon2.7GHz with 3.65GB of ram
Client:
C# client built on top of C api (libmysql.dll)

Description:
1. Initially I was running two services that bombarded mysql with inserts and selects. Ratio of inserts\selects is 1\10. (Later I figured even one is enough to kill mysql.)
2. Some of the inserts were invalid. They included columns not corresponding to table schema.
3. Half of the inserts used insert with update option
4. Inserts updated 3 tables 2 MyISAM and 1 Innodb
5. Innodb is the one that is getting corrupted
It was a question of minutes to kill the mysql server

I fixed inserts. All the inserts are proper now. That didn’t help much. Mysql server still crashes; it takes though longer 1-2 hours instead of minutes

Log/error log don’t show anything that could shade some light. Server dies quietly

Here the errors I see on the client side:
1. Lost connection to MySQL server during query
2. MySQL server has gone away
3. Initialy I was using 4.0.7 version of libmysql.dll/that got changed I moved to 5.0.13 version. Well it is still craching

So far I am unable to reproduce the problem using mysql-debug with debug option I'll keep on trying

How to repeat:
I don't have a good test case yet. I'll try to write one if time allows

Suggested fix:
No idea

Could you please feel free for to comment here when you
can provide a repeatable test case, for this bug to be will
open again.

Thanks in advance.

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