MySQL Bugs: #22816: Actions in 'Stored Procedure' tab causes server to go down with error

Bug #22816	Actions in 'Stored Procedure' tab causes server to go down with error
Submitted:	29 Sep 2006 9:14	Modified:	6 Oct 2006 15:08
Reporter:	Heinz Schweitzer (Gold Quality Contributor)	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Administrator	Severity:	S1 (Critical)
Version:	1.2.3 RC/1.2.4RC	OS:	Windows (XP)
Assigned to:	Mike Lischke	CPU Architecture:	Any

Description:
Actions in 'Stored Procedure' tab causes server to down with application error

Even after restart of the server it is no longer possible to access
any schema vai MySQL Administrator because, from now on the server will
allways go done.
The only thing left is to call phpMyadmin and to delete the curuptin schema 'aaa'
Then it works again

MySQL Administrator 1.2.3 RC
MySQL Server Information
--------------------------------------------------------------------------------
Connected to MySQL Server Instance
  Username:                root
  Hostname:                localhost
  Port:                    3306
--------------------------------------------------------------------------------
Server Information
  MySQL Version:           MySQL 5.0.18-nt via TCP/IP
  Network Name:            localhost
  IP:                      127.0.0.1
--------------------------------------------------------------------------------
Client Information
  Version:                 MySQL Client Version 5.0.11
  Network Name:            xxxxxxxxxxx
  IP:                      xxxxxxxxxx
  Operating System:        Windows XP
  Hardware:                Intel(R) Pentium(R) M processor 1600MHz, 512 MB RAM

How to repeat:

Open MySQL Administrator
Select Catalogs
create a new schema like 'aaa'
Select the new schema 'aaa'
In the right pane activate the 'Stored Procedur' tab
In there press the 'Create Stored Proc' button
A screen posp up like in screen shot s1
Here just press the red cross button in the upper right corner.
---> A MySQL SQl Editor window pops up offering you to create a function !!!
In line 3 in that window just enter 'return 1;' see screenshot s2
Press the 'Execute SQL'
--> You will get an Aplication Error from mysqld-nt.exe like
in screenshot s3
Try to select another schema
--> you will get an error like in screen shot s4

From here on the server is down. Below you will find an excerpt from the 
server logfile.
Even after restart of the server it is no longer possible to access
any schema vai MySQL Administrator because, from now on the server will
allways go done.
The only thing left is to call phpMyadmin and to delete the curuptin schema 'aaa'
Then it works again

060929 10:01:30  InnoDB: Started; log sequence number 0 1235696
060929 10:01:30 [Note] c:\wamp\mysql\bin\mysqld-nt: ready for connections.
Version: '5.0.18-nt'  socket: ''  port: 3306  MySQL Community Edition (GPL)
060929 11:05:28  InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
060929 11:05:29  InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 0 1235706.
InnoDB: Doing recovery: scanned up to log sequence number 0 1235706
InnoDB: Last MySQL binlog file position 0 0, file name 
060929 11:05:29  InnoDB: Started; log sequence number 0 1235706
060929 11:05:29 [Note] c:\wamp\mysql\bin\mysqld-nt: ready for connections.
Version: '5.0.18-nt'  socket: ''  port: 3306  MySQL Community Edition (GPL)

s1

Attachment: shot_5.jpg (image/jpeg, text), 95.91 KiB.

s2

Attachment: shot_6.jpg (image/jpeg, text), 93.92 KiB.

s3

Attachment: shot_7.jpg (image/jpeg, text), 94.93 KiB.

s4

Attachment: shot_8.jpg (image/jpeg, text), 88.91 KiB.

Thank you for the bug report. If I understand you then occurs a server crash,
and maybe it was a bug which was already fixed, could you please try with the last
server 5.0 release. Thanks in advance.

Have now:

MySQL-Server-Information
--------------------------------------------------------------------------------
Mit MySQL-Serverinstanz verbunden
  Benutzername:            root
  Hostname:                localhost
  Port:                    3306
--------------------------------------------------------------------------------
Serverinformation
  MySQL-Version:           MySQL 5.0.24a-community-nt via TCP/IP
  Netzwerkname:            localhost
  IP:                      127.0.0.1
--------------------------------------------------------------------------------
Clientinformation
  Version:                 MySQL Client Version 5.0.11
  Netzwerkname:            hgs
  IP:                      192.168.2.5
  Betriebssystem:          Windows XP
  Hardware:                Intel(R) Pentium(R) 4 CPU 2.00GHz, 504 MB RAM

The server crash no longer happens, but the other odd behaviour described
still applys.

Cheers
Heinz

Thank you for the feedback.

Thank you for your bug report. This issue has been committed to our source repository of that product and will be incorporated into the next release.

If necessary, you can access the source repository and build the latest available version, including the bug fix. More information about accessing the source trees is available at

    http://dev.mysql.com/doc/en/installing-source.html