I haven't been able to reproduce this bug with Firefox in Dapper or Edgy. I have tried various type of "catastrosphic" network failure while browsing with Firefox, and in every situation the browser get stuck while trying to connect to a new site it doesn't know the IP address, seems to give up after a long while, but in every case it never uses more that a few percent of my cpu usage.
Same thing when simply doing normal DNS lookup while the network is up ; I don't think I have seen any usage over 5% during the dns resolution. -- 100% cpu utilisation during DNS resolution https://launchpad.net/bugs/42217 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
