[Webkit-unassigned] [Bug 194028] Add limits to the amount of JavaScript that can be loaded by a website

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=194028

Alex Russell <slightlyoff at chromium.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |slightlyoff at chromium.org

--- Comment #7 from Alex Russell <slightlyoff at chromium.org> ---
Hey all,

My branch doesn't limit memory, but it applies a break on main-thread CPU in the form of a long-task limit. Currently, if you enable NSM, the entire page gets paused (no further tasks run until next input) if an individual main-thread script takes more than 200ms. This number is a total guess! It could be too high, or too low, and it doesn't do anything to limit recurring timers (a worry I don't have a reasonable approach for yet). It also doesn't apply any limits to script (or resources) in workers. The primary goal is to keep the main thread clean and create an opportunity to flag "this page is slow" UI of some sort (totally TBD).

I'm also unsure how to limit memory in an effective way without totally kneecapping games and implicating the graphics stack in hard-to-reason-about ways.

One of the unstated goals of NSM is to create a uniform policy, akin to TLS lock icon badging, that developers can easily understand compliance with at development time.

Would very much like to discuss tradeoffs if folks are interested!

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20190202/9348b9ad/attachment.html>