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

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Wed Jan 30 22:51:55 PST 2019


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

Maciej Stachowiak <mjs at apple.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |mjs at apple.com

--- Comment #3 from Maciej Stachowiak <mjs at apple.com> ---
WebKit currently does have some resource limits (at least on Apple platforms):

- Maximum memory limit per tab, and overall memory limit for all tabs. The memory limit is very high, though, because the counter-measure for violating it is your webpage gets killed, and the memory use requirements of many popular websites are very high. (Think top 10 rich web apps.) It is also much higher on macOS than iOS, and higher for foreground tabs than background.

- Maximum background CPU limit per tab (cap on Mac based on draining no more than ~1% of the battery, practically no ability to run in the background on iOS).


Things we currently do not have:

- CPU usage limits on the foreground tab
- Limits on the decoded or on-the-wire size of JavaScript or other resources
- Per-frame resource limits (so that ad frames could have a separate resource quota from the main content)

-- 
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/20190131/e597b197/attachment-0001.html>


More information about the webkit-unassigned mailing list