Bug #53721 Server crash
Submitted: 17 May 2010 23:54 Modified: 17 Jan 2012 17:26
Reporter: jaroslaw posadzy Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Server: Prepared statements Severity:S1 (Critical)
Version:5.1.45-Community OS:Microsoft Windows
Assigned to:
Tags: crash, data, execute, long, prepared, statement

[17 May 2010 23:54] jaroslaw posadzy
Description:
Server crash after packets (sended by my own client):
  - Com_Prepare:
      - query: "INSERT INTO table1(field1) VALUE (?)"
  - Com_Long_Data:
      - payload - 5 bytes (never mind)
  - Com_Execute
      - new_parameter_bound_flag = 0
      - type of parameters = (null or something - never mind)

Server crashing withoud sending any result

How to repeat:
I would like to receive e-mail with some information. It is important to develop .Net client
[18 May 2010 11:50] Miguel Solorzano
Thank you for the bug report. Could you please see and print here the possible call stack in the err file and provide a repeatable test case. Thanks in advance.
[18 May 2010 17:07] jaroslaw posadzy
Err file:

100518 18:56:28 [Note] Plugin 'FEDERATED' is disabled.
100518 18:56:28  InnoDB: Started; log sequence number 0 101628962
100518 18:56:28 [Note] Event Scheduler: Loaded 0 events
100518 18:56:28 [Note] C:\Program Files\MySQL\MySQL Server 5.1\bin\mysqld: ready for connections.
Version: '5.1.45-community'  socket: ''  port: 3306  MySQL Community Server (GPL)
100518 18:57:05 - 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=26214400
read_buffer_size=65536
max_used_connections=1
max_threads=100
threads_connected=1
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 58231 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd: 0x3820a00
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...
004E4069    mysqld.exe!String::numchars()[sql_string.cc:550]
004C7FC6    mysqld.exe!Item_param::convert_str_value()[item.cc:3138]
0055D09B    mysqld.exe!insert_params()[sql_prepare.cc:812]
0055DEC4    mysqld.exe!Prepared_statement::set_parameters()[sql_prepare.cc:3170]
0055F97C    mysqld.exe!Prepared_statement::execute_loop()[sql_prepare.cc:3229]
0055FB7B    mysqld.exe!mysqld_stmt_execute()[sql_prepare.cc:2482]
0045CBD5    mysqld.exe!dispatch_command()[sql_parse.cc:1189]
0045D6D7    mysqld.exe!do_command()[sql_parse.cc:878]
0047DEE0    mysqld.exe!handle_one_connection()[sql_connect.cc:1127]
0067E62B    mysqld.exe!pthread_start()[my_winthread.c:85]
0065DB33    mysqld.exe!_callthreadstart()[thread.c:293]
0065DBCC    mysqld.exe!_threadstart()[thread.c:275]
76E61194    kernel32.dll!BaseThreadInitThunk()
7749B3F5    ntdll.dll!RtlInitializeExceptionChain()
7749B3C8    ntdll.dll!RtlInitializeExceptionChain()
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 00000000=(null)
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.
[26 May 2010 5:50] Sveta Smirnova
Thank you for the feedback.

Please also send output of SHOW CREATE TABLE table1
[26 Jun 2010 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".
[17 Dec 2011 17:26] Valerii Kravchuk
Please, check if this problem still happens with a newer version, 5.1.60. If it does, please, send CREATE TABLE for the table used, as Sveta requested long time ago, and client (code or compiled) that demonstrates the problem.
[18 Jan 2012 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".