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: | |
| Category: | MySQL Server: Errors | Severity: | S3 (Non-critical) |
| Version: | 5.6.15 | OS: | Windows |
| Assigned to: | CPU Architecture: | Any |
[12 Jun 2014 22:55]
Mohsin Afzal
[13 Jun 2014 7:32]
Shane Bester
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]
Shane Bester
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".
Portions of this website are copyright © 2001, 2002 The PHP Group
Page generated in 0.053 sec. using MySQL 8.4.7-u6-cloud
Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the
respective copyright holders.
It is not reviewed in advance
by Oracle and does not necessarily represent the opinion of
Oracle or any other party.