MySQL Bugs: #13988: access violation & 100% cpu on start

Bug #13988	access violation & 100% cpu on start
Submitted:	13 Oct 2005 1:12	Modified:	21 Nov 2005 18:07
Reporter:	Matt Olson	Email Updates:
Status:	Can't repeat	Impact on me:	None
Category:	MySQL Query Browser	Severity:	S1 (Critical)
Version:	1.1.15, 1.1.17	OS:	Windows (windows server 2003 sp1)
Assigned to:	Jorge del Conde	CPU Architecture:	Any

Description:
Every time I start the Query Browser (after establishing the connection to the mysql server) the CPU immediately goes to 100% and the application fails to respond to the application close command.

In the status bar of the application it reads "Access violation at address 005B5358 in module 'MySqlQueryBrowser.exe'. Read of address 00000000"

The application is not completely unresponsive, but it doesn't do anything useful. It seems very confused. I cannot quit the application, and whenever I click on an interface element, such as the menu, or the schema definitions, the proper user feedback appears but then immediately disappears. For example, right clicking on a table definition causes the context menu to appear and then disappear immediately.

The only way to terminate the application is through Task Manager.

Note that this is based on a brand new installation of MySQL 4.1.14 via the windows-essentials package, and then installation of Query Browser 1.1.15 via the windows installer.

So far I have been unable to get Query Browser working at all.

How to repeat:
Just run Query Browser 1.1.15 on Windows Server 2003 SP1.

Suggested fix:
Look into race conditions, infinite loops, etc. There seems to be at least one access violation due to a read of a null pointer.

Hi!

I was unable to reproduce this bug using the latest Query Browser.  Is there any other information you can give us in order for us to reproduce this bug ?

Thanks!

I just downloaded browser 1.1.15 and installed it on my Windows 2003 Standard (SP1) machine with the same results.  My server is an AMT Athlon XP2200+ with 1GB ram.  I am running mySQL 4.1.9 and also have Administrator 1.1.3 and mySQL Control Center 0.94 (which I am using since Query Browser isn't working) installed.

confirming the same.
I'm running the uniform server http://www.uniformserver.com/ version 3.2a which bundles mysql Ver 4.1.12a
upon starting query browser CPU utilisation shoots up by 50%. It seems to be cnotinually throwing an exception. I'm attaching a screenshot.

oops, can't add a file! :(

I have the same results with query browszer 1.1.17.  I have mysql essential 5.0.15 for windows.

I downloaded and installed:

mysql-essential-6.0.15-win32.msi
mysql-administrator-1.1.4-win.msi
mysql-connector-java-3.1.11.zip
mysql-query-browser-1.1.15-win.msi

I get message "Access violation at address 005BEA40 in module 'MySqlQueryBrowser.exe'.  Read of address 0000000.

Symtoms are:  High CPU and unable to use any of the menus.  Like, I can't pull down the "file" menu, or the "Edit" menu.  And I have to use task manager to end the process.

Nothing is logged in the event logs.

Also, I'm accessing the computer using windows remote desktop.  I haven't tried it logging on direct at the comsole.  

I'm running this on Windows XP Pro SP2.

The same error with query browser 1.1.17. 

I get message "Access violation at address 005BEA40 in module
'MySqlQueryBrowser.exe'.  Read of address 0000000.

Symtoms are:  High CPU and unable to use any of the menus.  Like, I can't pull
down the "file" menu, or the "Edit" menu.  And I have to use task manager to end
the process.

 I'm accessing the computer using windows remote desktop.  I haven't tried
it logging on direct at the comsole.  

I'm running this on Windows 2003 Sp1.

I will echo the individuals comments here, I start the GUI(1.1.17) and as soon as I connect to the db server, CPU utilization shoots to 100% and the GUI becomes largely unresponsive, I can right click and will see the context menu for a split second then it disappears.  It's basically unusable.  I am able to close the app using the X in the upper corner of the application so it's not completely out but it's close.

Well, I had to reboot my Windows XP system and now it works OK.  I had not rebooted after it was installed on this system.  But, now after rebooting, it's been working.

On another XP system, it worked fine after install with no reboot.  I'll update this bug report if I have any more problems with it.

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

It appears that I'm not the only one to experience this problem. I don't know what other information I can provide to help you diagnose it. It's pretty simple. Install the program and run it -- it doesn't work.

To repeat: I'm on Windows Server 2003 with all the latest service packs and updates installed. I installed mysql-essential-4.1.14-win32.msi, then mysql-administrator-1.1.3-win.msi, then mysql-query-browser-1.1.15-win.msi. When I run the query browser, the CPU shoots up to 100% and the app is unresponsive.

I am also getting the same problem with the application. I installed version 1.1.17 then removed it and installed 1.1.14 and got the same error.  I have windows 2003 server with sp1 I am also having problems login on to my 4.1.15-nt MySQL instance I’m able to get a connect through ODBC but not java or php, this may be unrelated.

Bug report http://bugs.mysql.com/bug.php?id=15078 was marked as a duplicate of this one. 

By the way, I see nothing similar with both QB versions on plain XP, without any service packs. QB works great on old PIII 330 MHz with 256 MB of RAM. So, I believe, the problem, if any, has something to do with a conflict with some SP or Windows things like Remote access services...

It's true that I was accessing via Remote Desktop. I don't know if that has something to do with it or not. I don't have physical access right now, but next time I do, I'll try it from the console.

I just tested QB using remote desktop and everything worked as expected

I have also similar problems. Windows 2003 Server Standard - SP 1. MySql 5.0.15, QB 1.1.17, Administrator 1.1.5

First several days everything works nice. I use PC Anywhere and Remote Desktop for access. I have console access too, but use it very rarely.

One time I have logged to the QB, when I have clicked to a schema in the right pane, where schmas are located, computer was total blocked. After that I have tried several times (with Administrator too) and mainly computer was half or total blocked.

In error log I have not found nothing that seems to me to be problematic (Although I have not great experience with MySQL error logs).

I have reinstalled it and installed MySQL 4.1.14 and Administrator 1.1.4 (that combination works perfectly on my developer Win 2k machine), but problems are the same.

I have not idea what can be a problem. Is version 5.0.15 enough stable? Is problem with Remote Desktop or PC Anywhere access? What have I to do?

It seems to me that when I have performed other installations (for example ver. 4 after ver.5 was uninstalled, and next again 5) the installation process have had pretty shorter duration.

This problem have me very large headaches set.

Regards,
D.

I was also getting this exact issue.
A reboot solved it.
Installed: MySQL Server 5.0
Installed mySQL Administrator 1.1
Installed MYSQL Query Browser 1.1.17

Same error as above. Rebooted. Fixed! 
Good Luck.

(Windows Server 2003 via Remoted Desktop btw)

I too was experiencing the same problem:
Access violation at address 005BEA40 in module 'MySqlQueryBrowser.exe'. Read of address 00000000

Windows 2003 SP1
MySql Query Browser 1.1.17

STEPS TO REPRODUCE:
0) Remote desktop into Windows 2003 machine (from Windows XP) as admin
1) removed previous QB version
2) rebooted the PC
3) Remote desktop into Windows 2003 machine (from Windows XP) as admin
4) installed QB 1.1.17
5) started QB on remote desktop
6) enter username and password for 'root' user
7) enter connection information
8) clicked 'OK'
9) QB window opens with Access violation in status bar

It should be noted that when I rebooted the server, the problem went away.

Similar situation with QB 1.1.20 on Windows XP terminal services to Windows 2003 SP 1.  After restart the problem went away.

Having the same issues running Windows XP Pro 2002 Version service pack 2.
Can still execute stored queries. But using 100% of CPU resources, no menu abilities, can only "move" window on desktop small increments before you must re-grab window to move another increment. Slow to close window and seems to close when you remove focus from window (Click desktop, right click even its own icon on windows menubar). Also listing the above error code in the status bar.

Also note, I am not using windows remote desktop, this is on localhost. And restarting the machine did not correct issue.

Terminal Services to Windows 2003 Standard SP1...Reboot after installation resolved our problem as well.