41–50 of 107 posts
I'm not sure if this applies, but I really hope they provide better tools to identify badly behaving webpages. Sometimes when my CPU or memory are being cranked by Firefox, I really just want to kill the one tab out of 50 that's causing all the problems.
Earlier quoted context omitted.
Browse over to about:memory I run nightly and I don't use addons beyond adblock and don't run flash so perhaps my experiences are different, but I haven't had problems with Firefox leaking memory in a couple years. The profiling tools at about:memory may let you see where things are breaking.
Glad you mentioned about:memory. I usually read the changelog when they push out a release but somehow I missed that. This is a very nice breakdown of the memory.
I wish one of the most important tools for publishing and consuming text on the internet weren't so prone to problems as to require a dedicated health-reporting subsystem. My text editor and my email client don't need dedicated health-reporting subsystems.
Your text editor and email client aren't also capable of running arbitrary applications. Modern web browsers have more in common with operating systems than with text editors and email clients.
I wish one of the most important tools for publishing and consuming text on the internet weren't so prone to problems as to require a dedicated health-reporting subsystem. My text editor and my email client don't need dedicated health-reporting subsystems.
Your text editor and email client aren't also capable of running arbitrary applications. Modern web browsers have more in common with operating systems than with text editors and email clients.
That is the core of the problem right there. The need for a new health-reporting system is just a symptom or a consequence.
Earlier quoted context omitted.
It is rather unfortunate that there was a couple years there that FF lagged behind Chrome, it is really still having lasting impact on the brand. That said, the developer tools (both Firebug and the newer native ones) are really just not on par with Chrome now. I know they have people working on it, so I am looking forward to what they come up with.
The fact that there are both native and Firebug developer tools still baffles me- if they'd concentrated on one of the two they might be a lot more competitive with Chrome.
I wish one of the most important tools for publishing and consuming text on the internet weren't so prone to problems as to require a dedicated health-reporting subsystem. My text editor and my email client don't need dedicated health-reporting subsystems.
Your text editor and email client aren't also capable of running arbitrary applications. Modern web browsers have more in common with operating systems than with text editors and email clients.
Earlier quoted context omitted.
Your text editor and email client aren't also capable of running arbitrary applications. Modern web browsers have more in common with operating systems than with text editors and email clients.
>Modern web browsers have more in common with operating systems than with text editors and email clients. That is the core of the problem right there. The need for a new health-reporting system is just a symptom or a consequence.
Earlier quoted context omitted.
>Modern web browsers have more in common with operating systems than with text editors and email clients. That is the core of the problem right there. The need for a new health-reporting system is just a symptom or a consequence.
I rather like this fact. It allows things like GMail, YouTube and the fantastic work I see on the NY Times.
ADDED. An argument can be made that my operating system is already a system so complicated or unreliable that it requires its own specialized health-monitoring subsystem (of which Unix commands ps, free and top and OS X's Activity Monitor are a part). My response is that I resent having to deal with two such systems instead of only one.
I'm not sure if this applies, but I really hope they provide better tools to identify badly behaving webpages. Sometimes when my CPU or memory are being cranked by Firefox, I really just want to kill the one tab out of 50 that's causing all the problems.
It would be great if they could roll such a feature into a convenient UI. Just a magic "Firefox, whatever you are doing.. knock it off" button would be great. It could look at system memory usage and CPU usage, determine if either is high enough that it might cause user distress, and kill whatever tabs are the most likely offenders.
I have this type of issue more with Chrome than Firefox though and it always seems to be related to leaving a tab open with a video for a long time, even if it isn't being played.
Earlier quoted context omitted.
Your sqlite files might be locked - try either removing or moving them and copying them back.
I made a token gesture at fixing the sqlite files, but I don't have the patience to manipulate obscure files in AppData to get a browser to work. Stuff like this is why Chrome is my primary browser.
Both browsers have issues.