MySQL Bugs: #41415: Access violation when trying to edit table data

Bug #41415	Access violation when trying to edit table data
Submitted:	11 Dec 2008 23:26	Modified:	12 Jan 2009 11:01
Reporter:	Glen Zimmerman	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Administrator	Severity:	S3 (Non-critical)
Version:	1.2.15	OS:	Windows (xp sp3)
Assigned to:	Mike Lischke	CPU Architecture:	Any
Tags:	access violation, edit table data, regression

Description:
Database: MySQL 5.1.30-comunity via TCP/IP
MySQL Administrator 1.2.15

When I try to edit table data, I receive an access violation.

I uninstalled and then reinstalled with the same result.

Uninstalled and installed 1.2.12 which works fine. 

How to repeat:
Occurs everytime, even after restarting and going immediately to a database table to edit the data

Indeed, "Edit Table Data" gives a crash. Table (the only one in test database) was created like this:

C:\Program Files\MySQL\MySQL Server 5.1\bin>mysql -uroot -proot -P3310 test
Welcome to the MySQL monitor.  Commands end with ; or \g.
Your MySQL connection id is 1
Server version: 5.1.30-enterprise-gpl-advanced MySQL Enterprise Server - Advance
d Edition (GPL)

Type 'help;' or '\h' for help. Type '\c' to clear the buffer.

mysql> create table tt(c1 int primary key, c2 int);
Query OK, 0 rows affected (0.27 sec)

mysql> insert into tt values (1,1), (2,2);
Query OK, 2 rows affected (0.08 sec)
Records: 2  Duplicates: 0  Warnings: 0

I get the same error reproducibly.

MySQL 5.1.30 Community via TCP/IP
MySQL Administrator 1.2.15
MySQL Client Version 5.1.11
Windows XP Pro (SP3) 32 bit

Accounts affected: all
All tables were checked and verified OK.

Error message:
Exception EAccessViolation in module MySQLQueryBrowser.exe at 000CDD1D
Access violation at address 004CDD1D in module 'MySQLQueryBrowswer..exe'. Read of address 00000000.

Confirmed also.

Bug seems to occour on my system when a field that existed in the table is deleted and you then try and add another field. If you apply the change first, it applies correctly.

On my system, Vista SP1, it does not report an access violation, it simply reports "out of memory".

When using 1.2.14, instead of the currently installed 1.2.15, it reports it as an access violation.

Yes! i have the same problem!

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

Bug #42078 was marked as a duplicate of this one.

Bug #42145 was marked as a duplicate of this one.

Bug #42417 was marked as a duplicate of this one.