Fixes to memory footprint and garbage collection arrive in Firefox 7
1–10 of 44 posts
Re: Fixes to memory footprint and garbage collection arrive in Firefox 7
#2Re: Fixes to memory footprint and garbage collection arrive in Firefox 7
#3Re: Fixes to memory footprint and garbage collection arrive in Firefox 7
#4Nicholas Nethercote's blog has more technical details about the work he and others are doing to measure and optimize memory use in Firefox: http://blog.mozilla.com/nnethercote/category/memshrink/
Re: Fixes to memory footprint and garbage collection arrive in Firefox 7
#5Re: Fixes to memory footprint and garbage collection arrive in Firefox 7
#6They should have been working on these issues a long time ago. I think they are far more important than many of the new features that came with v5. The only thing holding many of us back from using FF is the memory issue. Good thing the FB debugger is so awesome, because that's the only thing that keeps bringing me back at this point.
Re: Fixes to memory footprint and garbage collection arrive in Firefox 7
#7Re: Fixes to memory footprint and garbage collection arrive in Firefox 7
#8I can't believe I just got called a "mom and pop beige-box surfer"...
Re: Fixes to memory footprint and garbage collection arrive in Firefox 7
#9They should have been working on these issues a long time ago. I think they are far more important than many of the new features that came with v5. The only thing holding many of us back from using FF is the memory issue. Good thing the FB debugger is so awesome, because that's the only thing that keeps bringing me back at this point.
Re: Fixes to memory footprint and garbage collection arrive in Firefox 7
#10They should have been working on these issues a long time ago. I think they are far more important than many of the new features that came with v5. The only thing holding many of us back from using FF is the memory issue. Good thing the FB debugger is so awesome, because that's the only thing that keeps bringing me back at this point.
Is FB better than chrome dev tools?
Sadly I think the world of Javascript debugging still has some way to go...