Bug #72992 MySQL Server Crashing
Submitted: 12 Jun 2014 22:55 Modified: 13 Jul 2014 11:06
Reporter: Mohsin Afzal Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Server: Errors Severity:S3 (Non-critical)
Version:5.6.15 OS:Microsoft Windows
Assigned to: CPU Architecture:Any

[12 Jun 2014 22:55] Mohsin Afzal
Description:
Hi 
I am facing MySQL server crashing issue, In MySql error logs I m not able to find any fruitful info but I am posting here in Event Viewer logging info for you guy's. Let me know if someone can help me on this issue.

Event Viewer Error:

Faulting application name: mysqld.exe, version: 5.6.15.0, time stamp: 0x52891132
Faulting module name: mysqld.exe, version: 5.6.15.0, time stamp: 0x52891132
Exception code: 0xc0000409
Fault offset: 0x00000000003ab23c
Faulting process id: 0xe60
Faulting application start time: 0x01cf8670b61f08b2
Faulting application path: C:\Program Files\MySQL\MySQL Server 5.6\bin\mysqld.exe
Faulting module path: C:\Program Files\MySQL\MySQL Server 5.6\bin\mysqld.exe
Report Id: 07060256-f264-11e3-945b-90b11c1d6870
Faulting package full name:
Faulting package-relative application ID: 

Thanks 

How to repeat:
I am not able to find the reason behind the issue till now so that's why i cant provide the reproducing steps.
[13 Jun 2014 7:32] MySQL Verification Team
Hi Mohsin!

Can you configure windows to write a minidump on next crash so we can analyze that.   Do you have any innodb fulltext indexes, I ask because that offset is in function fts_cache_find_wildcard (if I got the correct binary).

Is it possible you can try 5.6.19?
[13 Jun 2014 8:09] Mohsin Afzal
Hi Shane

Thanks for your response, Yes we are using innodb fulltext indexes in our database.

Thanks
Mohsin
[13 Jun 2014 11:06] MySQL Verification Team
If you can get minidump or stack trace at next crash, I can try confirm if problem is fixed in 5.6.19 or not.  Or feel free to upgrade and hope it is...
[14 Jul 2014 1:00] 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".