Just deployed the 23.4.5 agent to a few dozen endpoints and now seeing sustained high CPU (40-70%) from the SentinelOne processes on several machines. It's hitting our devs' workstations the hardest.
Anyone else seeing this? Feels like a resource leak. Rolling back the agent for now, but would love a known workaround or if S1 has acknowledged it yet.
Oh interesting, I was literally about to approve the update for my team this week. Thanks for the heads up. What kind of dev workstations are we talking about? Mostly Windows, or macOS too?
We have a lot of devs running Docker and local VMs, so high background CPU would be a huge problem for them. I'm curious if the issue is tied to specific workloads or if it's just a blanket resource hit.
Did you open a case with SentinelOne support yet? I wonder if they've published a known issue.
Yeah, we saw it almost entirely on Windows 10/11 workstations. The macOS machines in the same batch were totally fine, which makes me think it's a Windows-specific bug in the update.
Haven't opened a formal case yet, wanted to see if it was just us first. I'm checking their support portal now for a known issues doc, but no luck so far. If you've got a lot of devs with heavy local environments, I'd definitely hold off for a bit.
ian