Bug #20949 MYSQLD-NT.EXE USES 100% OF CPU USAGE
Submitted: 10 Jul 2006 19:41 Modified: 19 Aug 2006 7:39
Reporter: [ name withheld ] Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Server Severity:S1 (Critical)
Version:4.1.20 OS:Windows (WINDOWS 2000 SP4+)
Assigned to: CPU Architecture:Any

[10 Jul 2006 19:41] [ name withheld ]
Description:
I AM NOT A PROGRAMMER SO MY APOLOGIES IN ADVANCE

WE HAVE A P4 2Ghz, 2GB MEM, 36GB SCSI SERVER

WINDOWS 2000 SP4 AND ROLLOUTS

THE SOFTWARE COMPANY SUPPORTING OUR APPLICATION USES MYSQL 4.1, WHEN SPECIFIC PARTS OF THE APPLICATION ARE RUN (QUERIES) THE MYSQLD-NT.EXE SERVICE SHOOTS UP TO 100% AND USES A TRUCK LOAD OF MEMORY. EVERYTHING GRINDS TO A HALT AND WHEN THE QUERY IS CANCELLED IT TAKES A LONG TIME FOR THE RESIDULE CPU AND MEM TO BE CLEARED. ALTHOUGH THERE IS MUCH ABOUT SIMILAR PROBLEMS ON THE WEB, THERE IS NO REAL SPECIFIED SOLUTION.

How to repeat:
CAN ONLY REPEAT THROUGH THE APPLICATION
[10 Jul 2006 20:32] Valeriy Kravchuk
Thank you for a problem report. Please, specify the exact version, 4.1.x. And, if it is not 4.1.20, please, upgrade to 4.1.20 and check if the problem is still repeatable with it.
[12 Jul 2006 8:47] [ name withheld ]
We have loaded the 4.1.20 as the original was 4.1.1. This has resolved the issue, but I was wondering if anyone had any suggestions on some Tune Up parameters that would improve the Query?

Thank you for the prompt help, we really appreciate it.

Dave (Zimbabwe)
[12 Jul 2006 10:22] Valeriy Kravchuk
I am sorry, but the bug system is not the appropriate forum for asking help on using MySQL products. Your problem is not the result of a bug. Anyway, it is nice to know that version 4.1.20 solved your problem.

Support on using our products is available both free in our forums at http://forums.mysql.com/ and for a reasonable fee direct from our skilled support engineers at http://www.mysql.com/support/

Thank you for your interest in MySQL.
[14 Jul 2006 10:37] [ name withheld ]
As previously stated we upgraded from 4.1.1 to 4.1.20. This seemed to resolve the problem and we have operated trouble free for two days. Then blam! all of a sudden it startes doing the same thing. No-one has touched the Servers or changed a thing. Help I am at a loss!?!

Dave (Zimbabwe)
[19 Jul 2006 7:39] Valeriy Kravchuk
Send exact queries that give you the problem you described. We need a repeatable test case to be able to verify this as a bug.
[19 Aug 2006 23:00] Bugs System
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".