[webkit-help] Debugging Memory Leaks in WebKit

Simon Fraser simon.fraser at apple.com
Thu Mar 25 15:31:46 PDT 2021

The first step should be to figure out whether the memory is being triggered by page content; you can do that by inspecting the JS Heap via Web Inspector:

https://webkit.org/blog/6425/memory-debugging-with-web-inspector/ <https://webkit.org/blog/6425/memory-debugging-with-web-inspector/>

For code-level memory debugging, these are good starting places:
https://trac.webkit.org/wiki/Memory%20Use <https://trac.webkit.org/wiki/Memory%20Use>
https://trac.webkit.org/wiki/InvestigatingLeaksAndBloat <https://trac.webkit.org/wiki/InvestigatingLeaksAndBloat>

Once you know a bit more about the memory growth, report back and we can direct you.


> On Mar 25, 2021, at 3:03 PM, Joe Liccini <joliccin at microsoft.com> wrote:
> Hi WebKit Help,
> I am investigating what I believe is a memory leak in WebKit that is manifesting as high memory usage for Office 365 online apps (Word, Excel, PowerPoint, etc.) for Safari users.
> I have downloaded and built the source of WebKit, and by opening and closing a document or two, can very quickly get the memory utilization of WebKitWebProcess beyond 1 GB.
> I was wondering if anyone here has experience investigating memory leaks on WebKit? I can attach via the debugger but I'm not familiar enough with the code or tools to best identify common sources of memory leaks.
> Thanks!
> Joe

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-help/attachments/20210325/b80d972b/attachment.htm>

More information about the webkit-help mailing list