MySQL Bugs: #20089: Access Violation on Startup

Bug #20089	Access Violation on Startup
Submitted:	26 May 2006 10:36	Modified:	30 Jun 2006 19:42
Reporter:	John Bates	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Query Browser	Severity:	S2 (Serious)
Version:	1.1.20	OS:	Windows (Windows Server 2003)
Assigned to:		CPU Architecture:	Any

Description:
Immediately QB is started it displays the message: Access Violation at address 005BC7B4 in module 'MySqlQueryBrowser.exe'. Read of address 00000000.
The server CPU rises to a very high value. The message is displayed in the status bar and it looks as though it is being redisplayed many times a second.

I'm accessing the server with Remote Desktop and usage of both the program and the server becomes very difficult. MySQL is not installed on the C: drive, but on drive E:. MySQL Admin is also installed on drive E:.

If QB is minimised the CPU usage drops. Similarly, if a window is brought in front of the status bar to obscure it then CPU usage drops. Placing the Windows task manager (which stays in the foreground) in front of the status bar allows QB to be used which suggests that the CPU effort involved in refreshing the status bar with the message is causing the usage problem.

I have seen the same problem with earlier versions of QB on the same setup. I have tried re-installing QB on drive C: (instead of E:) and the problem still occurs.

How to repeat:
Just start up QB.

Suggested fix:
Fix the access violation!
Workaround!: use the Windows task manager as above.

I'm experiencing the exact same issue.  Running Win server 2003 accessing it via remote desktop.  startup QBrowser and immediatly get the same access violation message in the status bar and cpu utilization shoots way up (80-90%).  If you move any window in front of the status bar, utilization goes back to normal.  This looks to me like there's some issue with the screen refresh on the status bar or there's some kind of out of control loop going on when this access violation occurs.  Makes QBrowser pretty useless if you want to run it on a production box...

Hi!

I can't reproduce this bug.  QB seems to run fine in my Win2003 server.  Can you please delete the configuration files and see if that helps or not ?

Thanks a lot.

If by "install files" you mean the contents of the xml directory as was recommended in other posts about access violation errors - been there, done that.  That had no effect.

Are you testing this using a remote desktop contection to your win 2003 server?  that may be a factor...

Whoops, sorry, I meant "configuration files"...  been a long day!

Hi,

We're having the same problem here. We have installed MySQL Query Browser (version 1.1.20) on a Windows 2000 server platform (using local Admin account). Start Query Browser (connecting as root), error message "Access violation at address 005BC7B4 in model 'MySQLQueryBrower.exe'. Read address 00000000". Application is unusable, have to use stop process tree in task manager to quit.

Windows 2000 Server has service pack 4 installed, MySQL 5.0.22, Migration Tool kit 1.0.2.5, Administrator 1.1.9. No antivirus program installed at this time.

Have uninstalled and reinstalled a couple times but makes no difference.

Application is working fine on a Windows 2003 Advanced Server following the same install procedure of all MySQL related applications (above).

Any pointers would be appreciated…

Cheers, 
Steve

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

I have the exact same setup and the exact same problem described by John and Ben in previous posts.  I would try to delete the configuration files, but I'm working with a production system and would like to know exactly which files you might be referring to before going ahead with that.  This should be reopened.