I have been testing for some time to figure out why the Firewall control program has CPU spikes, and it's weird what I found out. After a fresh installation of version 126.96.36.199, without any previous user data, anything is just fine. CPU usage is completely harmless and not really worth a mention. But after adding many entries, for example above 100, it becomes quite alarming. Every single rule contributes to increased CPU spikes by the firewall control process. In version 188.8.131.52 this happens nearly every second and is consistently distributed over all those seconds. In the newest pre-release 184.108.40.206 a huge CPU spike happens after every 10 seconds, which seems to be the "monitoring timeout is increased up to 10 secs" change.
How to fix this CPU usage? The workaround is weird and it makes the impression it's a bug within the user interface. Open up the control application and type something weird into the rule filter, for example "lol". Now the rule list is empty because there are no rule matches. And now? Strangely the CPU spikes are fixed now! Typing something into the filter and then closing the control program works fine, and it makes me think this must be just a stupid user interface bug. Because ... why does it need to use so much CPU resources with many rules when the control program isn't even visible? I guess it must be a problem in the user interface thread. But I don't know if that's really the problem and I would like to let you know that this is actually a problem, so I'm posting. Would be nice if this is fixed in the future.
I'm adding some screenshots to this post. By the way, version 220.127.116.11 isn't affected. It's the version before the user interface got redesigned. Maybe there is a relation with this problem here? It makes sense for me. Windows 7 and 10 is affected, I tested it with both Windows versions.
Thanks in advance!