We’ve been making some decent headway with diagnosing the issue over here:
The thread goes on a bit, but tl;dr it looks like a bug in PMS’s parsing of SSDP replies from UPnP replies on the LAN and it’s been raised with engineering. Release notes for 1.14.1.5488 note “(SSDP) Better checking for invalid IP addresses in location field of SSDP XML”, which is when the high CPU behaviour first manifested.
