SshResident at 180% CPU: why my ScanSnap iX2500 took 14 seconds to start, and the fix that wasn't code
I'm Hisashi. I've run my own company for 22 years, and from 2011 to 2023 I ran it while moving between countries. Running a paperless company means I scan a lot of documents, and my main scanner had developed an annoying tic: I would press Scan, and nothing would happen. The scan button just blinked, ten to fourteen times, before the rollers finally started pulling paper. The scanner is a…
Hisashi, a businessman with two decades of experience running his own company, encountered an issue with his ScanSnap iX2500 scanner. Regardless of whether the connection was via WiFi or USB, and whether the save destination was a pop-up menu style or a fixed folder profile, the scanner would take several seconds to start scanning.
The problem was not the scanner itself or the connection, but the Mac operating system. Upon investigating, He discovered that the cause was a process called SshResident, which was occupying a full core of CPU while performing a task that increased in complexity with the number of applications running on the Mac. To resolve the issue, He wrote a small interposing library to cache the GetProcessInformation function calls, preventing the hundreds of unnecessary polls that slowed down the scanning process.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
