Bug #8192 Was working fine, but one day refused to open.
Submitted: 29 Jan 2005 9:24 Modified: 31 Jan 2005 17:30
Reporter: James DAVIS Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Query Browser Severity:S1 (Critical)
Version:1.1.5 OS:Windows (windows xp sp2)
Assigned to: CPU Architecture:Any

[29 Jan 2005 9:24] James DAVIS
Description:
Was working on VBA macros in MS word MS office home edition 2003, with an application connected by ODBC (ADO) to a  MYSQL database. Everything was working fine for some time, using the browser to check what was passing from word to the DB. I remember doing a query and getting a transation problem and I thought Oh maybe the macro is still running and I am using MyISAM. The application will never have more than one use.
Then I can't remember if it crashed or I closed it and then tried to restart it, but now it won't open. When I try to open it, it starts eating up nearly a giga of system memory until after about a minute it sends you a report and then I get this error message: "Exception EAccessViolation in libxml2.dll at 00045F0D
Access Violation at address 00965F0d in libxml2.dll. Write of address 100FC20"

How to repeat:
Just click on the desktop link or open the start programmes menu and click to open the browser.

Suggested fix:
I am going to try rolling back the system registers as soon as I can remember how to do it! Not really a fix!  And if that doesn't work use mysql control center.
[29 Jan 2005 13:57] James DAVIS
This is the same bug as 7832
[29 Jan 2005 14:54] James DAVIS
Obviously this is only critical as far as the query browser itself is concerned. I have tried:
uninstalling the browser rebooting, reinstalling the browser and rebooting;
stopping the database instance and opening the browser;
uninstalling the query browser, restoring system config to day before the problem started, rebooting, reinstalling the query browser;
uninstalling everything (mysql server 4.1, mysqladministrator 1.0.18, myodbc 3.5.10-2 and the query browser) restoring the system configuration to two days before prob started), uninstalling everything a second time (to get rid of what the restore operation had restored), reinstalled everything again
AND everything works except the query browser which refuses to open, eats nearly a giga of system memory and after about 10 minutes finally sends a memory report.
This is particularly worrying, because a permanent change has been made to my system configuration which a sys config restore does not eliminate. Although I have pretty good back up, I'm an amateur programme (professional translator) and this is my working machine.
[30 Jan 2005 6:26] James DAVIS
This is the same bug as bug 7832 which can be found here http://bugs.mysql.com/bug.php?id=7832&thanks=3
[31 Jan 2005 17:30] MySQL Verification Team
Duplicate of: http://bugs.mysql.com/bug.php?id=7832