Bug #19769 | Access Violation & Processor Hungry | ||
---|---|---|---|
Submitted: | 12 May 2006 13:14 | Modified: | 21 May 2006 12:06 |
Reporter: | Sean Pearce | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Query Browser | Severity: | S2 (Serious) |
Version: | MySQL 4.1.14-nt | OS: | Windows (Windows 2000 SP4) |
Assigned to: | CPU Architecture: | Any |
[12 May 2006 13:14]
Sean Pearce
[12 May 2006 13:17]
Sean Pearce
Task Manager during the login screen
Attachment: Screen Shot - Before.jpg (image/pjpeg, text), 101.43 KiB.
[12 May 2006 13:18]
Sean Pearce
Task Manager after login
Attachment: Screen Shot - After.jpg (image/pjpeg, text), 113.28 KiB.
[12 May 2006 13:33]
Valeriy Kravchuk
Thank you for a problem report. Please, try to repeat with anewer version of server (4.1.19) and QQuery Browser (1.1.20), and inform about the results.
[16 May 2006 7:45]
Sean Pearce
I have installed the highest revision of version 4 of MySQL Server (4.1.19), and the latest version of MySQL Query Browser (1.1.20). This has solved the problem, there is no more error message reported on the status bar and the processor is running at normal CPU usage. Thanks. This upgrade led to a second bug, which I found the answer to on the forums. When I installed the new version of MySQL Server, the service could not be started with an error of 0. After research on the forums I deleted ib_logfile0, ib_logfile1 & ibdata1 from "C:\<installation directory\data\" and this solved the problem. I now have a happy MySQL instance.
[21 May 2006 12:06]
Valeriy Kravchuk
Problem solved with upgrade.