After just 100 days, Google has lifted the veil of betaness off its web browser, Chrome, by releasing version 1.0. When Chrome made its first public appearance earlier this year, it was met with positive reveiws due to its JavaScript performance, as well as its robust multithreaded model. Now that the beta label has been ripped off Chrome, Google can't hide itself anymore: Chrome will now have to take Firefox and Internet Explorer head-on.
To view parent comment, click here.
To read all comments associated with this story, please click here.
Member since:2005-09-27
Member since:2005-07-24
I was just trying to figure this problem out as well. On BeOS Firefox would delay after loading any page other than the home page ( which I could navigate FULLY ) for up to a couple minutes.
The problem turned out to be that my system was setting my local router as the DNS, whereas I could set it further out in my extended network or use my ISPs DNS directly. This fixed the problem quickly.
Thing was, I could use almost all other networking tools without glitches, but noticed problems with two different IRC apps.
The exact cause of this, I cannot discern. It may have to do with how a network request is made, which would make sense why the platform mattered ( happened on BeOS & Haiku, but not Ubuntu, Vista, or MacOS X ).
Oh well, check your DNS - and set it manually ( I use the fastest OpenDNS servers I can find, bypassing all local DNS servers ( but not the DNS cache ) ).
--The loon
Member since:2006-03-16
This is because the Firefox GUI is single-threaded. The plugin uses the same thread as Firefox and when it has a hard time loading the movie from youtube it hogs the thread.
Considering that Chrome wants to isolate everything to separate processes I guess they've done that with plugins as well, which means only the plugin gets stalled.
So to sum up: If you ever plan to do some heavy lifting, single threading things are not the way to go.
Member since:
2008-12-12
Actually I had a very similar problem with Firefox. As it turned out, it was not Firefox at all, but instead was my router. Once I upgraded the firmware, the problem went away.