You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 811059e
Browse filesBrowse the repository at this point in the historyBrowse files
CodeBlock should do a better job accounting for extra memory it allocates.
https://bugs.webkit.org/show_bug.cgi?id=225068
Reviewed by Mark Lam.
Source/JavaScriptCore:
Right now we aren't telling the JS GC about the extra memory
attached to CodeBlocks. It looks like on at least some sites this
can be a fairly large percentage of the total memory retained by
the JS object graph.
* bytecode/CodeBlock.cpp:
(JSC::CodeBlock::visitChildren):
(JSC::CodeBlock::JITData::size const):
* bytecode/CodeBlock.h:
* jit/JITCodeMap.h:
(JSC::JITCodeMap::memorySize const):
Source/WTF:
Small convenience function to help compute the memory used by a Bag for JS GC
accounting.
* wtf/Bag.h:
Canonical link: https://commits.webkit.org/237039@main
git-svn-id: https://svn.webkit.org/repository/webkit/trunk@276610 268f45cc-cd09-0410-ab3c-d52691b4dbfc
0 commit comments