[Webkit-unassigned] [Bug 160497] MemoryPressureHandler shouldn't know how to release WebCore memory

[bugzilla-daemon at webkit.org]

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

--- Comment #35 from Darin Adler <darin at apple.com> ---
(In reply to comment #34)
> (In reply to comment #31)
> > Safari uses both legacy WebKit (WebKit1) and modern WebKit (WebKit2). Some
> > day it might get to the point where it has no dependency on legacy WebKit,
> > but at the moment it still uses both.
> 
> Anywhere I can learn about why Safari still needs legacy WebKit and what it
> uses it for? That's really surprising to me and I'm curious!

I don’t think there is anywhere to learn that, but I am willing to disclose a little bit: At some point in the recent past, there was some use of legacy WebKit in some of the Safari Browser Extension support.

Also, keep in mind that WebKit is a system framework on macOS; Safari can invoke some other macOS framework and nothing prevents that framework from using some bit of WebKit API for some task.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.webkit.org/pipermail/webkit-unassigned/attachments/20161111/00f5ca31/attachment.html>