On Oct 25, 2012 8:42 PM, "Domenic Denicola" <dome...@domenicdenicola.com>
wrote:
>
> The new thing this proposal brings to the table is the ability to mark,
from within your code, exactly what object you're worried about the
leakiness of. You also get very understandable error messages for
determining who's using that object. Pouring through the list of retained
objects, trying to find the one you're concerned about by looking through
ambiguous short names or via the profiler's deep tree hierarchy, is not
nearly as straightforward.
But don't you get that by just changing one line to
var obj = undefined;
?
jjb
_______________________________________________
es-discuss mailing list
es-discuss@mozilla.org
https://mail.mozilla.org/listinfo/es-discuss
