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: | |
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
[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