61–64 of 64 posts
104 MB at the moment. For me at least, Slack really got their shit together sometime last year and improved the issue significantly. I still remember having to restart Slack twice a day, but it ain't issue anymore.
- Slack: 103.8 MB
- Slack Helper: 61 MB
- Slack Helper: 459.1 MB
- Slack Helper: 549.6 MB
- Slack Helper: 264.9 MB
Total = 1.4384 GB for only 3 Slack channels on macOS High Sierra
Pretty absurd.
No, that's the default slack experience if you have a lot of teams. I recommend: * Disabling emoji support, especially animated emojis> * Disabling auto-expanding of images (gifs are egregious) * Use compact display * Limit number of channels/groups you're in if possible, surely you don't need all those channels. Doing this curbed my resource usage quite a lot. I don't miss emoji's all that much.
You need to put it in context. Is system ram under pressure? Poor memory performance is measured by swap i/o or bandwidth, not usage.
If you have 16gb of ram and little else using the ram then there is nothing to worry about. If you have 4gb of ram then a support ticket is probably your best course of action rather than whining to random forums.
To answer your question, runtimes will lazy garbage collect because you might want the data again. Decompressed images and frame buffers lead to faster under interface interaction. You're not using a terminal app, you're using an app that can render any font or image in complex ways to an image buffer, for rendering at 60fps with smooth scroll. Are you also on a retina display?
Earlier quoted context omitted.
Same. The web client has feature parity with the desktop client so I haven’t understood why people bother with the latter.
For me, cmd + tabbing to a chat application is a much better user experience than having to dig through open tabs and/or multiple instances of the browser.