I’ve noticed lately in my iStats Menu, that the longer my Mac runs without restarting, Textexpander’s memory usage slowly increases. Jumping into Activity Monitor, there are no less than 8 processes for Textexpander.
Are there any reasons for this? I expect browsers to be memory hogs, but am surprised to see Textexpander (8.4.1) hot on their heals, that’s all.
I checked in with engineering on this. Turns out the multiple processes are by design. TextExpander runs separate UI components for the main window, Quick Actions, fill-in windows, etc., and macOS isolates each one as its own process. Same way browsers handle tabs. That’s been the architecture for a while, so nothing new in 8.4.1.
As for the memory climbing over time, some gradual increase between restarts is standard macOS behavior for long-running apps. The numbers in your screenshot are within a normal range for what’s running. If it ever starts impacting performance, restarting TextExpander will reset things.
Thanks for investigating and the reassurance. But, as per your initial reaction, this does ‘feel’ extremely bloated to just perform text expansion. And its memory usage definitely climbs faster than other apps do following a restart. With so many apps going non-native these day, be it bloated Electron or otherwise, it’s very easy to gobble up RAM with just a few of them open along with a browser. I may give Rocket Typist a spin to see if that has a smaller footprint.
This is your space to ask questions, find support, and share ideas with fellow TextExpander users and our product team. As a first step, take a moment to introduce yourself to the community.
