[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 13:02:16 PST 2019


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

Simon Fraser (smfr) <simon.fraser at apple.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |simon.fraser at apple.com

--- Comment #2 from Simon Fraser (smfr) <simon.fraser at apple.com> ---
It's really hard to impose CPU limits unless you run JS in a separate thread or process, to which you can assign priority. Doing so is something we've thought about, but it's a large engineering effort.

It's possible we could track memory use on a per-document basis, but there are all sorts of code paths that can trigger memory use (often by code not controlled by webkit), and again it's hard to track all that.

-- 
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/20190130/83b63df3/attachment.html>


More information about the webkit-unassigned mailing list