CHROME UTC CLOCK UPDATE
CHROME UTC CLOCK DOWNLOAD

Furthermore I’m not keen on how FF is constantly timing out while it’s not doing anything useful, ideally it would schedule a background timer instead of maintaining it’s own clock as it appears to be doing with “gettimeofday”. The “poll(…)” is FF checking if any of it’s descriptors have input (I have no idea what these descriptors are, other than 4).ĭev Commentary: The read call is totally redundant with the poll call and should only be triggered by the poll. It returns EAGAIN because this is a non-blocking socket with no input. The “read(4…)” is FF checking the X-server for input. Given your problem, you will see FF blocked on one single call for >20s, or you will see it looping over a sequence of calls for >20s.įor me, while it’s running normally, I see this over and over again. If yes, then FF is receiving input but is not acting on it. While it’s hung, check if moving the mouse causes spurious events. If CPU activity is normal, then it implies firefox is waiting for IO for some reason, you could try “strace firefox” to see exactly what it’s trying to do. Is there any disk/network/cpu activity happening in the meantime? This happens every time you start FF (and not just once per day/session)?

The value is stored in milliseconds, so perhaps try a value of 60000 (60 seconds). On some systems the default value for this parameter (10 seconds) causes some problems. Try increasing the parameter under about:config. I can imagine it being more of that for people who needs to restart browser/PC often, though. It’s a nuisance, but since I only fire up the browser like once a day it’s not that big deal for me. After those 30 seconds though it doesn’t do that again. I have no idea what causes it, but I get similar experience: whenever I fire up Firefox for the first time it’s useable for a few seconds, then completely locks up for about 30 seconds during which it won’t respond to anything. That way, no-one would moan about the major version changing because that would only happen at least 12 months apart!ĭoing my usual browsing habits opening tabs, typing a search query, then it suddenly very slow, I can’t even click the tabs and I have to wait for 10 to 15 secs. 2011.01 for the first release of the year and so on – gives them 99 releases a year, which should be more than enough).

I think Mozilla should have done a year.release version scheme (e.g. So, yes, Firefox increases its major version number at about the same rate as Chrome, but like Chrome, just learn to ignore the version number really.

CHROME UTC CLOCK UPDATE

This is why you see people whine incessantly about new Firefox releases (normally every 6-8 weeks unless there’s an emergency fix) and no-one complains about the many more updates Chrome gets (every 2 weeks typically).Īlso don’t forget that IE on Windows often gets a monthly update as part of the “Patch Tuesday” – again, more often than Firefox, but no-one complains about that either (mainly because MS don’t bother changing the major version number and it’s “bundled” with a bunch other updates, which are often all automatically applied). However, although they’ve been copying some of Chrome’s features recently (and not all the copied Chrome ideas have been good ones, mind you), Mozilla has yet to copy the idea of “silent updating” that Chrome uses.

CHROME UTC CLOCK DOWNLOAD

And Chrome inflating itself to version 14 (and updating itself far more often) is surely “twice as worse” than Firefox is? It is interesting to note how Mozilla is beginning to “hide” the version numbers of its products – the download buttons no longer reveal the version and if they could remove it from the “About…” box, I bet they would!

Chrome utc clock