Objective Development Forums

Very interesting. I have no explanation for this. Note that the traffic meter in the menu bar is driven by Network Monitor as a summary of all items. You might have had a filter active so that not all items were visible, or you might have had the mouse in the window so that animations are paused and...

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 bit...

When something is blocked, Network Monitor flashes the connection line in red. Drill down to a specific connection line by clicking disclosure triangles. Then right-click the line to get a context menu. Choose "Show corresponding rules" to see all rules which match the line, or hold down t...

These are your kexts NOT from Apple: Index Refs Address Size Wired Name (Version) UUID <Linked Against> 146 0 0xffffff7f8158b000 0x4000 0x4000 com.squirrels.driver.AirParrotSpeakers (1.8) 8DC45570-251F-3FED-9FF4-3400209F0D2C <124 5 4 3> 155 0 0xffffff7f80d07000 0x3f000 0x3f000 com.paragon-software.f...

Do you have the map in Network Monitor open? The map is the only thing which requires the GPU.

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

Without the kext running, Little Snitch cannot do anything to your network traffic. Can you please check with



in a Terminal window that it is indeed removed? If it is removed, the problem is not related to Little Snitch.

Copy the following lines and paste them into the Rules window of Little Snitch Configuration:

action: allow
direction: incoming
priority: regular
process: /usr/sbin/mDNSResponder
owner: me
destination: any
port: any
protocol: any

This rule allows mDNSResponder to accept any incoming connections.

Interesting. Maybe the NVIDIA Web Drivers were not activated for whatever reason? Or something has been updated so that the library signed by NVIDIA is no longer required?

Ah, you're using this kext hack mentioned before. Yes, NVIDIA drivers will work in this case. It's just that we cannot recommend a hack, especially if system security must be weakened in order to use it.

Interesting. Is it possible that you are working with Apple's drivers on the other drive, not with NVIDIA's web drivers? BTW: The flickering will be fixed in 4.0.4 (next nightly). It turned out to be an image filter in the inspector pane. If the window contains an other view with a filter, the map f...

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 ...

We have not coded anything in any way which requires an additional driver. It's just that we use the map. It's a component ready-made by Apple and if you drop it into your UI, the app needs the GPU and thus the driver. As long as you don't open the map, Network Monitor displays well, even with NVIDI...

You should be able to silence the notification by deciding (with a rule) how to handle them. When you allow any incoming connection for mDNSResponder permanently, you should never see this message again. If you do, please report the details to our support, reporting this as a bug. If you want to all...

Can you please mail us a crash log in support?