There is a workaround here: Local UI shows cloned sites as running even when stopped - #4 by burt
The fix involves cleaning up incorrect data within the
sites.json file which can be found within Local’s configuration folder for you specific OS:
Kinda strange my last 2 versions of Local (5.10.5+5403) and before show some sites as running right when I open the app even tho I did not ‘start’ them, also when I click on Stop all when I’m finished it says they are stopping but they really don’t. It doesn’t seem to affect anything.
** Interesting these are always the same sites and are the last most recent sites I started.
Is this a harder tax/stress on my laptop to have all of those extra sites running?? These same sites keep running even tho I’m not doing anything with them throughout the day…
** I’m on a newer Windows 10 laptop and the latest version of Local