Test the network from the lowest level if you haven’t already, using ping
and the IPv4 address of a common server (for instance, ping 8.8.8.8
) to bypass DNS.
If it works, your DNS is borked.
If it doesn’t, then there’s something more fundamentally wrong with your network configuration—I’d guess it was an issue with the gateway IP address, which would mean it can’t figure out how to get to the wider Internet, although it seems super-weird to have that happening with DHCP in the mix. Maybe you left some vestiges of your old configuration behind in a file that your admin GUI doesn’t clean up and it’s overriding DHCP, I don’t know.
On Linux, the OOM reaper should come for the memory cannibal eventually, but it can take quite a while. Certainly it’s unlikely to be quick enough to avoid the desktop going unresponsive for a while. And it may take out a couple of other processes first, since it takes out the process holding the most memory rather than the one that’s trying to allocate, if I recall correctly.