<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED FIXED - MemoryPressureHandler shouldn't know how to release WebCore memory"
href="https://bugs.webkit.org/show_bug.cgi?id=160497#c36">Comment # 36</a>
on <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED FIXED - MemoryPressureHandler shouldn't know how to release WebCore memory"
href="https://bugs.webkit.org/show_bug.cgi?id=160497">bug 160497</a>
from <span class="vcard"><a class="email" href="mailto:mcatanzaro@igalia.com" title="Michael Catanzaro <mcatanzaro@igalia.com>"> <span class="fn">Michael Catanzaro</span></a>
</span></b>
<pre>(Note: I've removed this patch from the list of proposed backports for 2.14 because it is a huge refactor. r208975 can still easily be backported, the code just moved from one file to another.)
(In reply to <a href="show_bug.cgi?id=160497#c35">comment #35</a>)
<span class="quote">> 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.</span >
Interesting!</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>