What you are seeing are names for well-known ports. Like port 80 being HTTP or port 443 being HTTPS. Or rather, what someone decided the name should be, because port 1110 isn’t “nfsd-status”. Either way, this does not mean Chrome is suddenly speaking NFS or anything like that.
You can check the list yourself, here
These ports are used by Chrome because it uses the operating system’s ephemeral port range. By default, starting from Windows Vista, this is 49152-65535. However, on your system, it was changed to be 1024-65535. This is not necessarily a malicious change.
You can change it back using an elevated command prompt:
netsh int ipv4 set dynamicport tcp start=49152 num=16384
netsh int ipv4 set dynamicport udp start=49152 num=16384
netsh int ipv6 set dynamicport tcp start=49152 num=16384
netsh int ipv6 set dynamicport udp start=49152 num=16384
However, this will not solve any hangs or whatever. You should open a new question about that, with further investigation about which websites (HTTP, HTTPS, …) are affected, whether it’s working on a different PC/smartphone/tablet on the same network, whether other browsers on the same PC are affected….
Keep in mind that depending on the Chrome extensions/apps you have installed, the process may remain in the background for quite some time.
Also, I suggest not using any third-party security software at all.
netsh int ipv4 show dynamicport tcp
(run it in Command Prompt).