[Webkit-unassigned] [Bug 221530] Safari browser fails to set boundaries to Wasm application memory

[bugzilla-daemon at webkit.org]

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

--- Comment #2 from Keith Miller <keith_miller at apple.com> ---
Whoops accidentally submitted while typing my response. Anyway...

I don't think a hard limit is really what we want or what a modern API for memory management would do. Rather, it would be better, IMO, if there was a memory warning event that fires as you approach high memory. But even that won't solve all the problems. For example, on iOS the OS is free to kill any process it wants for using too much memory (too much memory is decided based on system pressure not a fixed limit). Even on Mac it's hard to predict if a tab will go over it's memory budget since 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/20210210/54d05e04/attachment-0001.htm>