MySQL Bugs: #25783: Access violation prevents Query Browser from loading catalog schema

Bug #25783	Access violation prevents Query Browser from loading catalog schema
Submitted:	23 Jan 2007 15:04	Modified:	8 Mar 2007 2:39
Reporter:	Adam Wood	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Query Browser	Severity:	S3 (Non-critical)
Version:	1.1.20	OS:	Windows (WinXP Pro SP2)
Assigned to:	Assigned Account	CPU Architecture:	Any

Description:
When loading MySQL Query Browser (usually by right-clicking a table in Administrator and choosing "Edit Table Data", every so often a combination of the following three error messages appears:

(1) "Access violation at address 00914FE4 in module 'LIBMYSQL.DLL'. Read of address 000003AC" [in the status bar at the bottom of the Query Browser Window]

(2) "Access violation at address 00352C16 in module 'libmysqlx.dll'. Read of address 0000028C" [as a message box - in both (1) and (2) the addresses are sometimes subtly different]

(3) "Could not load schema tables ... MySQL Server has gone away (2006)" [as a message box]

After these messages the table contents may show correctly, although sometimes it fails to show entirely, and the table listing in the rightbar is almost always missing. It only seems to occur when opening MySQL Query Browser, and usually can be rectified by closing and re-opening the application.

How to repeat:
This problem occurs erratically and seemingly randomly but can be observed when opening MySQL query browser with a query pre-loaded (ie by choosing "Edit Table Data" from a table's context menu in MySQL Administrator).

Sorry, typo in title - fixed now

Thank you for the bug report. Could you please try with latest released version
1.2.9. Thanks in advance.

I have just installed Query Browser 1.2.9 (RC) and the problem persists: I received an error message identical to those detailed above but with the two addresses in the message being 0096D717 and 00000088, respectively. Again, the problem is not critical as it is possible, after a period of slowness or possibly an application hang, to restart Query Browser and experience normal behaviour.

Thank you for the feedback. I still was not able to repeat with my
own table and data, could you please provide a dump of a table which
presents that behavior on your side?. Thanks in advance.

I am experiencing this same problem. I installed the "Windows (x86) ZIP/Setup.EXE" v.5.0.27 and the "Windows (x86)" GUI Tools v.5.0-r9a yesterday on Windows Vista.

All other features seem to be working fine.

I did find that opening the MySQL Query Browser from the Windows Start menu (rather than right clicking the table in the MySQL Administrator and clicking Edit Table Data) works fine every time.

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".

Bug #27066 was marked as duplicate of this one

Bug #26230 seems to be duplicate of this one.

No specific table is needed to cause this problem. Here's a generic table that does it on my system:

CREATE TABLE `cfwwebtools`.`test` (
  `testid` INTEGER UNSIGNED NOT NULL AUTO_INCREMENT,
  `testname` VARCHAR(45) NOT NULL,
  PRIMARY KEY(`testid`)
)
ENGINE = InnoDB;

No table content needed. Once the table shows up in the MySQL Administrator catalog table list, right-clicking on it and selecting "Edit Table Data" from the context menu opens the MySQL Query Browser and pops up an error dialog stating "Access violation at address 0093D717 in module 'LIBMYSQL.DLL'. Read of address 00000088" with an OK button. After clicking the button the Schemata pane at the right side remains at "Fetching Data..." under the selected catalog/database. Right-clicking the catalog name and selected "Refresh" from the context menu usually loads the schemata as one would expect it to do without interaction.

As others have stated, opening the Query Browser from a menu does not seem to give the trouble; only when it is preloaded with a query as in when right-clicking on a table and asking to edit the table data and the browser preloads with a "select * from [tablename]" query.

Windows XP Pro Service Pack 2; MySQL Query Browser version 1.2.6 beta (although it sounds like other people are having the same issue with 1.2.9); MySQL Administrator version 1.2.6 rc (ditto); and default installation for all.