Bug #9942 Access Violation

• Submitted: 15 Apr 2005 20:08
• Modified: 31 May 2005 20:35
• Reporter: G Schaeffer
• Status: Can't repeat
• Category: MySQL Query Browser
• Severity: S1 (Critical)
• Version: 1.1.6
• OS: Windows (Windows 2003)
• CPU Architecture: Any

[15 Apr 2005 20:08] G Schaeffer

Description:
Query Browser receives error message:
"Access violation at address 005B1054 in module 'MySQLQueryBrowser.exe'" on start, immediately after connecting.  I have tried deleting the xml files in the Documents and settings/[user]/mysql directory as well as reinstalling newly downloaded installations.

How to repeat:
Install on the same environment?

Suggested fix:
None.  Not fixed.

[16 Apr 2005 0:29] Jorge del Conde

Hi,

I can't reproduce this bug-report under WinXP/2000.  Can you tell me what mysql server version are you connecting to ?  Thanks!

I'll try 2003 in a while.

[16 May 2005 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".

[31 May 2005 19:37] Shane Moore

I experienced this problem as well. Windows 2003 Server. Works fine on Windows XP Pro.

[31 May 2005 19:40] Shane Moore

OS: Windows 2003 Server - SP1
MySQL: 4.1.12-nt

MySQL Administrator 1.0.20 works fine. Logging into the server locally using MySQL Browser 1.1.9 results in an access violation. The application locks up and takes 90+ CPU. You need to kill the browser process.

[31 May 2005 19:57] Shane Moore

Also, this is ONLY with the installer. Using the zipped version seems to work ok.

[31 May 2005 20:00] MySQL Verification Team

I was unable to repeat the behavior reported with QB 1.1.9 on
Windows 2003 Server standard Edition and QB installed using
the installer.

[31 May 2005 20:09] Shane Moore

I can easily repeat it on 3 windows 2003 servers. Unreal.

[31 May 2005 20:34] MySQL Verification Team

QB Working on Windows 2003 Server

Attachment: bug9942.PNG (image/png, text), 112.42 KiB.

[31 May 2005 20:35] MySQL Verification Team

I attached a picture showing QB working on Windows 2003.

[1 Jun 2005 0:04] Shane Moore

I dumped the browser and moved to phpmyadmin. After using the zipped version of the browser and reinstalling the installed version, the installed version doesn't give an access violation but is unusable due to the query field being messed up. phpmyadmin works flawlessly and is adequate for my needs.

[29 Jul 2005 16:50] Wei Feng Zheng

I also just installed the Query Browser on a newly built Windows 2003 SP1 using the MSI package and it kept crashing on me with the message about address violation in module 'MySQLQueryBrowser.exe' in the status bar. 

I took Shane Moore's advice about using the Zip file instead of the MSI install and it works. However, as Shane mentioned, now there is a problem with the query field. Anything I type in the field is invisible. There is not even a cursor to let you know that you are focused in that area. After typing in some jibberish and hitting Execute, I got an error message about SQL syntax error from my jibberish so at least then I knew it was accepting my input; it was just invisible. I tinkered with the Options settings and finally I got the Query field to show up by changing the Code Font from the default of Bitstream Vera Sans Mono to something else (It was Courier New in my case).

So for those people trying to get Query Browser to work on Windows 2003 SP1, use the Zip package and change the default Code Font to something else and you should be ok.