This network service is still problematic. It's resource-hungry at the best of times but for some reason it more than doubles it's consumption after time. this is probably due to some interaction with other services. I haven't managed to catch it go from less hungry to ravenous yet so can tell you why. I know that another upnp app produces similar strain when running but that doesn't add and leave a service so it is only an issue when it needs to be. Ie running.
For me the issue would go away if rmc removed or switched off the service when the application exited.
thanks
Bookmarks