WiFi Guard hogs CPU after reconnecting to network
1 post
I have been using WiFi Guard since 2013, and I have never seen the following behavior until I updated to the current version: 26.10.
When I'm not using the Internet, I disconnect my laptop from my home network. After I reconnect my laptop to my network several hours later, my laptop appears to be locked up and unresponsive. I run Windows Task Manager and it shows my CPU usage as 98% and WiFi Guard hogging all of the CPU time at 98%. I then go to WiFi Guard and click on the red Stop Now button. As soon as the red Stop Now button returns to the blue Scan Now button, my laptop's CPU usage drops from 98% back down to below 10% and all is good.
When I run a WiFi Guard scan by clicking the Scan Now button, the scan uses a peak 22% CPU usage for less than 5 seconds. I'm OK with this.
But when I disconnect my laptop from the network for, say, 8 hours, and then reconnect the laptop to the network, WiFi Guard goes into this strange mode where it scans the network indefinitely and hogs all the CPU time, and stays that way until I press the red Stop Button.
I never saw this behavior before version 26.10.
Anyone else experience this behavior?