[ Date Index ] [ Thread Index ] [ <= Previous by date / thread ] [ Next by date / thread => ]
On 15/04/14 10:26, Philip Hudson wrote: > On 64-bit debian testing. > > Firefox has been running fine on this host forever, but in the last > couple of days it now runs as expected immediately after launch and > for a short while thereafter, then effectively stops fetching. > Comet/Ajax/auto-refresh pages don't refresh, manual reloads and new > pages don't load, but, and this is the real problem, nor do they > timeout, meaning you have no idea that there is a problem until other > symptoms present themselves. Maddening. > > Something on the order of 20 tabs spread across 4 windows. htop shows > plenty of RAM and CPU available. > > After quitting, which seems visually to complete correctly, a process > called 'firefox.real' is left running. > > I haven't checked rigorously, but a first pass seems to show no such > problems visible with character-mode browsers on the same host nor > with Safari on a Mac on the same subnet with the same proxy and DNS > settings. (Subject to revision). > > I'm hoping somebody recognizes these symptoms before I go down all the > different possible routes there are for resolving this. > cat /usr/bin/firefox.real On Debian this is a shell script that checks for "real" firefox and then launches IceWeasel instead, which is broken. This is the single most stupid thing on Debian, and you should excise it as soon as possible by installing a proper Firefox instead, preferably a nightly version. I'm running 31.0 on Debian right now, and it works perfectly with a similar amount of tabs and windows to your count right now. With a *lot* of plugins. Regards *disclaimer: I spend a lot of my working life building firefox on Linux, specifically Debian. I'm pretty used to it's foibles. -- The Mailing List for the Devon & Cornwall LUG http://mailman.dclug.org.uk/listinfo/list FAQ: http://www.dcglug.org.uk/listfaq