canmove, Confirmed users, Bureaucrats and Sysops emeriti
1,334
edits
Line 10: | Line 10: | ||
Building these tools would also provide infrastructure useful for users who want to answer questions like "Why is Firefox using so much memory right now?" or "Which of the 20 tabs I have open is making Firefox slow?". Giving users the ability to answer these questions will also put some additional pressure on Web authors to write applications efficiently. | Building these tools would also provide infrastructure useful for users who want to answer questions like "Why is Firefox using so much memory right now?" or "Which of the 20 tabs I have open is making Firefox slow?". Giving users the ability to answer these questions will also put some additional pressure on Web authors to write applications efficiently. | ||
I'd like to focus particularly on discussing possible architectural approaches for memory debugging tools, since that's something that I think we need to solve, but one I really don't know how to solve. | I'd like to focus particularly on discussing possible architectural approaches for memory debugging tools, since that's something that I think we need to solve, but one I really don't know how to solve. I'd also like to discuss how much overhead we're willing to take in order to properly "blame" performance and memory usage. | ||
== Agenda == | == Agenda == |