21–30 of 107 posts
Funnily enough, Firefox died on my system today and I haven't been able to get it working since. Just freezes after start up, even in safe mode (well, when it even booted up, which it stopped doing after a couple tries).
On my computer it sometimes doesn't open a window unless I open a second instance of Firefox, and then both suddenly load. Try that maybe?
Funnily enough, Firefox died on my system today and I haven't been able to get it working since. Just freezes after start up, even in safe mode (well, when it even booted up, which it stopped doing after a couple tries).
Your sqlite files might be locked - try either removing or moving them and copying them back.
Stuff like this is why Chrome is my primary browser.
My text editor and my email client don't need dedicated health-reporting subsystems.
Will this help them figure out that they need to fix memory leaks?
They're already fixing memory leaks. In fact, Firefox now uses less memory than Chrome. Let me guess, you're another person who hasn't used Firefox in a few years hasn't bothered to check out the latest versions at all? :)
And yes, I am using the latest build, I check about:memory regularly, stripped out the unneeded add-ons, but maybe I've just got too much stuff open and those pages have lots of script activity.
Is my usage the issue or is there something that can be improved in my scenario?
Part of this is somewhat similar to how Windows 8 measures "Start-up impact" of applications that auto-start, and allows you to disable them with two clicks. (In task manager)
Internet Explorer will even tell you how long each plugin takes to start. You can see the stats in [Gear icon]-> Manage Add-ons. My slowest plugin is actually Google Chrome Frame :p
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.
Earlier quoted context omitted.
They're already fixing memory leaks. In fact, Firefox now uses less memory than Chrome. Let me guess, you're another person who hasn't used Firefox in a few years hasn't bothered to check out the latest versions at all? :)
For me, alas, with 5 windows open and many, many tabs per window, Firefox regularly climbs into the 1 Gig+ memory range. The solution: less windows and tabs, I guess. But I was hoping / expecting the memory profile to change significantly over the past few builds. And yes, I am using the latest build, I check about:memory regularly, stripped out the unneeded add-ons, but maybe I've just got too much stuff open and th…
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.