When youâre done working in Local do you generally Stop all of your sites and then quit the application? Some users have found that this helps prevent this error from cropping up.
Another thing you can try is opening the Windows Task Manager and killing any MySQL entries that appear. After that, you can try restarting the site.
Hey @Nick-B youâre always so fast to reply! Generally I have not been stopping sites. I did just try it and if I stop the site before closing and reopening Local it is able to start the site again. If I know I need to reopen local, Iâll start doing this.
I only made a bug report as it seemed like it was fixed when you guys released 9.2.2 as for a few months I havenât seen this issue. I was just working on that external theme addon which caused me to open and close local a ton so I kept running into this.
We did add some changes to help curb these type of errors which were a lot more frequent before 9.2.2 (notes here Releases - Local)
That said, itâs been tricky to get rid of forever, thatâs why I mentioned the workflow to try and avoid it by ensuring things are stopped and closed down each time.
If it continues to crop up or you hit any other snags please keep us posted however!
