Win 10 Task Manager shows 2 instances of mysqld process
My Windows 10 shows 2 instances of mysqld processes running.
cmd> tasklist /fi "imagename eq mysqld.exe" shows:
Image Name PID Session Name Session# Mem Usage
================== ============== ========= ==========
mysqld.exe 5656 Services 0 7,620 K
mysqld.exe 7804 Services 0 354,208 K
I do not use more than one mysql instance. When I installed MySQL initially,
it showed up in the Services list and I set it to run Automatically.
I never run anything from the command line involving invocation.
For each of the processes above I ran:
cmd> Get-WmiObject Win32_Process -Filter "name = 'mysqld.exe'" | where {$_.ProcessID -eq 5656 }
__PATH : \\SCOUT\root\cimv2:Win32_Process.Handle="5656"
Caption : mysqld.exe
CommandLine : "C:\Program Files\MySQL\MySQL Server 8.0\bin\mysqld.exe" --defaults-file="C:\ProgramData\MySQL\MySQL Server 8.0\my.ini" MySQL80
__PATH : \\SCOUT\root\cimv2:Win32_Process.Handle="7804"
Caption : mysqld.exe
CommandLine : "C:\Program Files\MySQL\MySQL Server 8.0\bin\mysqld.exe" "--defaults-file=C:\ProgramData\MySQL\MySQL Server 8.0\my.ini" MySQL80
One of these instances is a dud -- the pid 5656.
You can see that one of the instances was invoked wrong.
See the odd double-quote differences for the command line information.
My installs are:
Windows 10 version 2004
MySQL 5.8.16
MySQL Workbench 8.0
I've been using MySQL for years. I did the Windows 10 2004 feature update just a few days ago.
I think (??) that before that I would only see one instance of mysqld in the Task Manager.
Here is one real problem, not just an observation:
I cannot stop the mysql service using the Services list. It gives up with failure because the action timed out.
The Services list shows only 1 instance, but the Task Manager shows 2 items.
Perhaps the system is confused on which to close or how to do both --- ?
I can successfully kill both processes from the Task Manager.
I think this may be making my system RESTART action **very slow** since closing down the mysqld processes is troublesome.
If I restart the computer, both instances show up right away.
Even with the detailed Get-Wmi-Object info, there is no indication of who/what starts each instance.
Is this process something started by how mysql is initiated, or does Windows initiate it?
Seems something has a bug in the initiation of mysql. Is it MySQL or Windows or ???
Subject
Views
Written By
Posted
Win 10 Task Manager shows 2 instances of mysqld process
5016
July 18, 2020 12:20PM
1209
July 18, 2020 01:19PM
1404
July 20, 2020 08:10AM
1036
July 21, 2020 10:00AM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.