# Bug Summary
Local WP intermittently freezes and becomes completely unresponsive, occasionally requiring a full system restart to regain functionality.
# Steps to Reproduce
Install Local WP on a MacBook Pro with multiple macOS user accounts.
Use Local WP under both users (not simultaneously).
Switch between users or open Local WP on one user while it may have been previously opened on the other.
Observe that Local WP begins to hang, freeze, or cause the entire system to slow down.
In some cases, the system becomes so unresponsive that a full restart is required.
So far I’ve not been able to reproduce intermittent freezes or unresponsive UI in Local when using it logged into two macOS user accounts. I tried with both fast user switching and normal log out-and-in.
One thing to check is that you’re running the Apple Silicon version of Local on your M1 MBP. We’ve had reports of freezes and slow UI for users on Apple Silicon who were accidentally running the Intel version of Local.
You can check the Local app like this:
Command-click the Local app icon in your dock (or otherwise browse to it in the Applications folder).
Right-click the app icon and choose “Get Info”.
You should see “Apple silicon” or “Intel” next to “kind”. If you do not see “Apple silicon”, download the latest Apple Silicon version from the Local releases page: https://localwp.com/releases/
I did run into other issues using Local from two macOS user accounts (such as 500 errors when viewing sites if Local was running in both sessions), but only when fast user switching. This is due to macOS sharing certain resources between user accounts, such as open ports and the /etc/hosts file. I found that logging out instead of fast-switching between users helped with these issues, since this quits Local in one user session before opening it in another.