I also think that this makes sense. Can we already start thinking about countermeasures, though?
It looks to me that catching a long-running/infinite microtask loop is much easier to detect and interrupt than a long-running sequential loop. However, if we wish to pause a page with such a microtask loop to display some UX, trigger a breakpoint or even to leave some CPU to other pages in the same process, is there anything specific we need to do to guarantee that no network/user input/layout/apz... can be processed during the interrupt? Cheers, David On 14/01/16 00:35, Ehsan Akhgari wrote: > I think this makes sense. _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
