Bug
1614612 [wpt PR 21728] - Update performance.measureMemory to the latest proposal, a=testonly
Automatic update from web-platform-tests
Update performance.measureMemory to the latest proposal (#21728)
* Update performance.measureMemory to the latest proposal
This changes the result format of the API to the latest version of
the proposal at https://github.com/ulan/performance-measure-memory.
Specifically, the result format changes from JS only and per-frame:
{
total: {
jsMemoryEstimate: 200*MB,
jsMemoryRange: [100*MB, 300*MB]
},
current: {..},
other: [..]
}
to more a generic format with breakdown:
{
bytes: 70*MB,
breakdown: [
{bytes: 40*MB, globals: 2, type: 'js', origins: ['foo.com']},
{bytes: 30*MB, globals: 1, type: 'js', origins: ['bar.com']}
]
}
Additionally this patch skips extension contexts and relaxes
cross-origin memory measurement for site-isolated pages.
Bug:
1049093
Change-Id: I997bfe9f6008eaedd0ce5010839232ef3540cad0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/
2047028
Commit-Queue: Ulan Degenbaev <ulan@chromium.org>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Cr-Commit-Position: refs/heads/master@{#740671}
* Add long timeouts for three slow tests
* Empty commit to try repushing
Co-authored-by: Ulan Degenbaev <udegenbaev@gmail.com>
Co-authored-by: Luke Zielinski <44509484+LukeZielinski@users.noreply.github.com>
--
wpt-commits:
4cc7a3e996059acc69edd1bfa9a0b95cd1da1b13
wpt-pr: 21728