Bug #62405 mysqld.exe!?check_next_symbol@Gis_read_stream@@QAE_ND@Z()
Submitted: 10 Sep 2011 8:00 Modified: 10 Nov 2011 23:14
Reporter: Fajar Adianto Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Server: Errors Severity:S1 (Critical)
Version:5.5.8 OS:Microsoft Windows (MS Windows XP SP 2)
Assigned to: CPU Architecture:Any
Tags: mysql 5.5.8

[10 Sep 2011 8:00] Fajar Adianto
Description:
After I upgraded mysql from 5.0.37 to 5.5.8 community server, I frequently have my mysql service (on Windows XP SP2) crashed. The error log was pasted below. Might this be caused by some bad queries? The queries from my software ran just fine on previous version. Please help.

110906 13:34:45 - mysqld got exception 0xc0000005 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help diagnose
the problem, but since we have already crashed, something is definitely wrong
and this may fail.

key_buffer_size=16777216
read_buffer_size=262144
max_used_connections=8
max_threads=151
thread_count=2
connection_count=2
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 133447 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd: 0x2536f80
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
005BD67A    mysqld.exe!?check_next_symbol@Gis_read_stream@@QAE_ND@Z()
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 025D42C0=<SOME QUERY>
thd->thread_id=1
thd->killed=NOT_KILLED
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.

How to repeat:
Mysql service can be restarted after the error occured. But after undeterminable period, it crashed again. I can run the queries included in the error log, and it executes just fine.
[10 Sep 2011 9:34] Valeriy Kravchuk
Please, check if the same problem still happens with a newer version, 5.5.15.
[10 Oct 2011 23: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".
[11 Nov 2011 7: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".