• Omer Katz's avatar
    cppgc: Clear large pages on free. · 1fc24069
    Omer Katz authored
    Destroyed large pages can be reallocated before the OS get a chance to
    reclaim and clear them. In such cases we will get non-zero memory in a
    newly allocated page.
    Normal pages are not affected since they are kept in page pools instead
    of being freed.
    Fix by explicitly clearing the payload when destroying a large page.
    
    Bug: chromium:1056170, chromium:1206274
    Change-Id: I6436302f50b8f0b4ef41288425bf464b0eb52d5f
    Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2874404
    Commit-Queue: Omer Katz <omerkatz@chromium.org>
    Reviewed-by: 's avatarMichael Lippautz <mlippautz@chromium.org>
    Cr-Commit-Position: refs/heads/master@{#74418}
    1fc24069
Name
Last commit
Last update
..
benchmarks Loading commit data...
cctest Loading commit data...
common Loading commit data...
debugger Loading commit data...
debugging Loading commit data...
fuzzer Loading commit data...
fuzzilli Loading commit data...
inspector Loading commit data...
intl Loading commit data...
js-perf-test Loading commit data...
memory Loading commit data...
message Loading commit data...
mjsunit Loading commit data...
mkgrokdump Loading commit data...
mozilla Loading commit data...
test262 Loading commit data...
torque Loading commit data...
unittests Loading commit data...
wasm-api-tests Loading commit data...
wasm-js Loading commit data...
wasm-spec-tests Loading commit data...
webkit Loading commit data...
BUILD.gn Loading commit data...
OWNERS Loading commit data...