31–40 of 107 posts
Earlier quoted context omitted.
Guys, maybe we shouldn't be feeding the trolls...
You would rather have the statement remain unopposed, as if fact?
...and it worked
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.
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? :)
While I feel Mozilla has tried to address the memory leaks, I still think there is a lot of memory bloat for my usage.
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…
There can be a very drastic difference between "virtual memory made visible to a process" and "physical memory actually used by a process", especially in the context of shared memory systems where you have 5+ processes that are able to share much of their text and data segments.
I don't have Firefox here so I forget, but does their about:memory page show the "proportional" memory usage? KDE's KSysGuard has a detailed memory usage calculator that can display stats like that.
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.
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? :)
I use Firefox everyday as one of my main browsers. On version 20 right now and expect to be updated to 21 the next time I restart it. I've installed the "Memory Restart" add on, so that memory use stay reasonable. Once the memory size hits 900MB, I see performance decline. Over 1GB and I start to see the Beach Ball of Death. My typical usage is to have 2-3 windows open with 3-6 tabs open in each window. While I feel…
What extensions do you have? I've also disable Java, Shockwave, etc. Try Nightly? I've never had a single stability issue.
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.
Have you tried out the about:memory page? It doesn't do CPU, but it is a good way to see what particular pages are hogging memory.
Earlier quoted context omitted.
You would rather have the statement remain unopposed, as if fact?
Trolls don't care about facts but get off on people replying to their posts which is why HN has user voting of comments... ...and it worked
> and your browser can start healing itself I wonder what some specifics are for this statement.
Using the data that is being collected today, we can analyze poor performance and stability and correlate it with certain extensions and plugins, going down to the level of version and platform specifics. We can then provide better blocklisting based on this data, in addition to providing the user with the tool to see the results for themselves and offer suggestions such as updating an add-on or uninstalling it.
Earlier quoted context omitted.
I use Firefox everyday as one of my main browsers. On version 20 right now and expect to be updated to 21 the next time I restart it. I've installed the "Memory Restart" add on, so that memory use stay reasonable. Once the memory size hits 900MB, I see performance decline. Over 1GB and I start to see the Beach Ball of Death. My typical usage is to have 2-3 windows open with 3-6 tabs open in each window. While I feel…
I'm using Nightly with AdBlock and vimperator. I see around 600MB RAM usage with 2 or 3 windows and 5-6 tabs. What extensions do you have? I've also disable Java, Shockwave, etc. Try Nightly? I've never had a single stability issue.
Other people mentioned the about:memory tab. Taking a look at it now, I'm seeing about 80-100MB difference between what that tab say and what the activity monitor says.