4.0.3 has huge memory and CPU footprint in High Sierra

General discussions about Little Snitch
gspot
Posts: 3
Joined: Sun Feb 19, 2012 8:14 pm

4.0.3 has huge memory and CPU footprint in High Sierra

Postby gspot » Tue Oct 10, 2017 5:34 pm

Anyone else notice this?

energia
Posts: 2
Joined: Tue Oct 10, 2017 6:01 pm

Re: 4.0.3 has huge memory and CPU footprint in High Sierra

Postby energia » Tue Oct 10, 2017 6:02 pm

Show some screenshots of the footprint?

philby
Posts: 2
Joined: Wed Oct 15, 2008 10:56 pm

Re: 4.0.3 has huge memory and CPU footprint in High Sierra

Postby philby » Thu Oct 12, 2017 9:34 am

Before rebooting yesterday evening Little Snitch Netzwerkmonitor used ~1.5GB memory on my system, after 12 hours (8 of which with no user activity) it again up to almost 1 GB.
Image

Numanmania
Posts: 1
Joined: Mon Oct 16, 2017 7:49 am

Re: 4.0.3 has huge memory and CPU footprint in High Sierra

Postby Numanmania » Mon Oct 16, 2017 7:51 am

Same here on High Sierra 10.13 and LS 4.03 above 100% CPU all time.

christian
Objective Development
Objective Development
Posts: 1436
Joined: Thu Nov 09, 2006 11:46 am

Re: 4.0.3 has huge memory and CPU footprint in High Sierra

Postby christian » Mon Oct 16, 2017 2:26 pm

The memory consumption of Network Monitor is primarily due to the map. It looks bad, but is not that bad because most of the memory is a cache for rendered graphics. This cache is freed when an other app needs more memory. As long as there is no pressure, the map keeps the cache.

The CPU load is an other issue. We are aware of it and are working on a fix. This high load occurs when you run applications with a particular connection pattern, e.g. wallets for digital currencies or similar.

imyself
Posts: 2
Joined: Fri Nov 10, 2017 9:45 pm

Re: 4.0.3 has huge memory and CPU footprint in High Sierra

Postby imyself » Mon Nov 20, 2017 10:07 pm

the same problem here. especially cpu. snitch 4.0.3 eats all my battery life on my new mbp on High sierra, for example when I was streaming a video.

christian
Objective Development
Objective Development
Posts: 1436
Joined: Thu Nov 09, 2006 11:46 am

Re: 4.0.3 has huge memory and CPU footprint in High Sierra

Postby christian » Tue Nov 21, 2017 12:39 pm

Can you please try 4.0.4 nightly? We have improved performance for certain network traffic patterns in this version.

gspot
Posts: 3
Joined: Sun Feb 19, 2012 8:14 pm

Re: 4.0.3 has huge memory and CPU footprint in High Sierra

Postby gspot » Tue Nov 21, 2017 4:20 pm

CPU usage is fine in the nightly but memory usage is still way too high. Higher then kernel_task for me. 2.82GB vs 2.25 for kernel_task

christian
Objective Development
Objective Development
Posts: 1436
Joined: Thu Nov 09, 2006 11:46 am

Re: 4.0.3 has huge memory and CPU footprint in High Sierra

Postby christian » Tue Nov 21, 2017 4:35 pm

I suppose this is for Network Monitor. When you close the map and force-quit Network Monitor, it will re-open automatically with the map closed. How much is the memory usage then?

I'm asking because the map is a standard user interface component which is not under our control. It caches rendered bitmap images as long as there is enough free memory. If you have lots of RAM and no other app needs it, that may be a huge amount. It will be freed at the moment an other app needs memory, so it should be harmless.

twilsonco
Posts: 1
Joined: Fri Feb 09, 2018 10:35 pm

Re: 4.0.3 has huge memory and CPU footprint in High Sierra

Postby twilsonco » Fri Feb 09, 2018 10:37 pm

I'm on version 4.0.5 on High Sierra on a mid-2012 MBPr with 8GM memory, and currently my Little Snitch Network monitor is consuming 7.79GB of memory. Hope this issue hasn't been closed because it's still very much a problem.

dmz
Posts: 1
Joined: Wed Mar 21, 2018 10:10 am

Re: 4.0.3 has huge memory and CPU footprint in High Sierra

Postby dmz » Wed Mar 21, 2018 10:12 am

4.0.5 on High Sierra here as well, on a 64 GB Mac Pro 2010 tower... and Little Snitch Network Monitor was using _24 GB_ of memory just now before I quit it. That's... pretty extreme, even if it will be freed as soon as any other app needs memory.

christian
Objective Development
Objective Development
Posts: 1436
Joined: Thu Nov 09, 2006 11:46 am

Re: 4.0.3 has huge memory and CPU footprint in High Sierra

Postby christian » Wed Mar 21, 2018 10:31 am

We would be glad to fix this, but as long as we use Apple's MapKit, we must live with all of its features. The only workaround is to avoid using MapKit in the first place. You can do this by keeping the map closed (never opening it). The map is allocated the first time it's opened.

durandal42
Rank 1
Rank 1
Posts: 25
Joined: Wed Aug 09, 2017 9:35 pm

Re: 4.0.3 has huge memory and CPU footprint in High Sierra

Postby durandal42 » Sat Jun 02, 2018 10:52 pm

Leaving the map closed doesn't help: Little Snitch Network Monitor's memory usage still creeps upwards, typically consuming several GB of ram before I get annoyed and kill it.

If this is "working as intended" with use of MapKit, can we have an option to disable the map entirely?

christian
Objective Development
Objective Development
Posts: 1436
Joined: Thu Nov 09, 2006 11:46 am

Re: 4.0.3 has huge memory and CPU footprint in High Sierra

Postby christian » Mon Jun 04, 2018 10:34 am

When memory consumption is high, can you please first open Console.app, select your device under "Devices", enter "Snitch Network Monitor" as a search term to reduce the amount of log messages to the relevant ones. Then open a Network Monitor window and hit Cmd-Option-Ctrl-Shift-M. This prints memory usage statistics to the Console. That's the amount of memory we allocate for connection caching and traffic statistics.

What I want to find out is whether this is actually MapKit eating up the memory (which I doubt if you never opened the map), legitimate connection caches (you could limit those in the Preferences) or maybe a memory leak somewhere.

durandal42
Rank 1
Rank 1
Posts: 25
Joined: Wed Aug 09, 2017 9:35 pm

Re: 4.0.3 has huge memory and CPU footprint in High Sierra

Postby durandal42 » Tue Jun 05, 2018 5:21 am

Here's the chunk of log messages that appeared in ~/Library/Logs/Little Snitch Network Monitor.log when I invoked that key command:

Code: Select all

2018-06-04 20:16:22.012 Little Snitch Network Monitor[67906:2431291] #### object allocation statistics: ####
2018-06-04 20:16:22.012 Little Snitch Network Monitor[67906:2431291]             LSMDataModel:        1 208 bytes each
2018-06-04 20:16:22.012 Little Snitch Network Monitor[67906:2431291]         LSMConnectionSet:       -3 88 bytes each
2018-06-04 20:16:22.012 Little Snitch Network Monitor[67906:2431291]     LSMSummaryConnection:    32417 240 bytes each
2018-06-04 20:16:22.012 Little Snitch Network Monitor[67906:2431291]        LSMTrafficHistory:      509 1976 bytes each
2018-06-04 20:16:22.012 Little Snitch Network Monitor[67906:2431291]          LSMProcessGroup:      245
2018-06-04 20:16:22.013 Little Snitch Network Monitor[67906:2431291] ----- Connections in Live Set: -----
2018-06-04 20:16:22.013 Little Snitch Network Monitor[67906:2431291]      Logical Connections:    20026
2018-06-04 20:16:22.013 Little Snitch Network Monitor[67906:2431291] Peer Summary Connections:    11476
2018-06-04 20:16:22.013 Little Snitch Network Monitor[67906:2431291]  Dom Summary Connections:      642
2018-06-04 20:16:22.013 Little Snitch Network Monitor[67906:2431291]  App Summary Connections:      120
2018-06-04 20:16:22.013 Little Snitch Network Monitor[67906:2431291] ----- Other: -----
2018-06-04 20:16:22.013 Little Snitch Network Monitor[67906:2431291]    LSMPhysicalConnection:     7598 (0 null, 0 inactive)
2018-06-04 20:16:22.013 Little Snitch Network Monitor[67906:2431291] LSMTrafficHistory (live):      509
2018-06-04 20:16:22.013 Little Snitch Network Monitor[67906:2431291]         2.81 MB bytes for objects
2018-06-04 20:16:22.013 Little Snitch Network Monitor[67906:2431291]         1.81 MB in 7522 32-bit sections
2018-06-04 20:16:22.013 Little Snitch Network Monitor[67906:2431291]         0 B in 0 64-bit sections
2018-06-04 20:16:22.013 Little Snitch Network Monitor[67906:2431291] #### end statistics ####


At approximately the same time, Activity Monitor reported the following memory usage statistics for Little Snitch Network Monitor:
Memory: 5.47 GB
Compressed Memory: 3.75 GB
Real Memory Size: 1.76 GB
Virtual Memory Size: 10.01 GB
Shared Memory Size: 47.0 GB
Private Memory Size: 1.72 GB


Return to “Little Snitch General”

Who is online

Users browsing this forum: Google [Bot] and 5 guests