- From: <bugzilla@jessica.w3.org>
- Date: Sun, 21 Aug 2016 20:10:42 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=20567
Olli Pettay <bugs@pettay.fi> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |bugs@pettay.fi
--- Comment #77 from Olli Pettay <bugs@pettay.fi> ---
(Hmm, I don't know what happened to my comment here. I did write one on Friday.
Perhaps didn't press Save Changes. Anyhow, it was something like...)
Memory management is rarely being discussed when adding new APIs to the
platform. But given the history of rather bad memory leaks even in major web
sites (Google Reader is/was a canonical example of how to leak everything,
every single global of every single article loaded to it, and currently Twitter
seems to suffer from something similar occasionally). I think we should take
memory management more seriously, either by designing APIs so that writing
leaky JS is less likely or by mitigating the issues. This bug is about the
latter.
--
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Sunday, 21 August 2016 20:10:50 UTC