Same issue. Is anybody able to reproduce this? What steps are needed, or which actions are done by the users?

Hi, we're running into the same issue. Here's another batch of of IPs that caused the alert to be displayed `2a05:d01c:384:f300:8979:1146:915a:7586 2a05:d01c:384:f300:1f03:8f13:3db8:5734 2a05:d01c:384:f301:4855:df7a:ef82:c708 2a05:d01c:384:f301:c624:fc1e:1f8c:d6ad 2a05:d01c:384:f301:5745:abc8:a63b:930b 13.42.57.219 13.40.30.100 18.130.230.186 52.56.60.39 3.8.216.162`

Adding a launch argument "-OS_ACTIVITY_MODE disable" has fixed the high cpu usage in my case.