MySQL Bugs: #8573: Access violation in module libmysqlx.dll

Bug #8573	Access violation in module libmysqlx.dll
Submitted:	17 Feb 2005 16:14	Modified:	21 Sep 2005 14:10
Reporter:	Douglas Green	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Query Browser	Severity:	S3 (Non-critical)
Version:	1.1.5	OS:	Windows (Windows XP)
Assigned to:	Michael G. Zinner	CPU Architecture:	Any

Description:
Error that I get when discarding or applying changes.  Not serious since I can work around it.  Status line says, "Access violation at address 0035CE63 in module 'libmysqlx.dll'.  Read of access 00000020".  Then whenever I run another select query it gives an "Unapplied changes" popup.

How to repeat:
1. Run a select query.
2. Manually edit some of the rows.
3. Change the select query and try to run it.
4. It asks you whether to apply or discard the changes.
5. Click discard (I may have clicked 'Abort' the first time).
6. Now every time you change the query and try to run it again, you get the Unapplied Changes popup (even though changes have already been discarded), and the Access violation appears in the status bar.

Suggested fix:
Not sure, but wanted MySQL to be aware of this.

Thank you for the bug report.

Hi,

  I am also having the same problem. I am using Mysql 4.1.9 and Query Browser Version 1.1.5. This error is occuring while trying to Edit the value in the Resultset. 

Thanks in advance and looking for the sulution.
Renjith

The problem doesn't seem to happen if a SELECT is not narrowed (SELECT * will work just fine) and a SELECT a,b,c ... will create an Access violation in module libmysqlx.dll.

Click on one of schema then while it is expanding its tree, quickly click on another schema.  Access violation occured. All schema after the last schema was selected is inaccessible with same access violation error.  I am able to expand or collapse the last schema accessed before access violation error appeared.

I've the same problem after creating a new database on mySQL (5.0.11-beta-nt) log in with a user into. The next popup error is showed when the MySQLQueryBrowser tries to fetch data from the selected schema:
Access violation at address 00396B60 in module 'libmysqlx.dll'. Read of address 00000000

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 bugfix, yourself. More information 
about accessing the source trees is available at
    http://www.mysql.com/doc/en/Installing_source_tree.html

The bug appeared in v1.1.18 too, when I clicked on a database of another host (a slave host exactly).
But this bug isn't regular...