measure-memory

edit

WPT coverage of the tests of measure-memory at the revision c8fa86fb13d4. The tests link to their results in the browsers on wpt.fyi. The tentative tests (experimental features), the reftests and the crash tests are listed separately from the stable tests.

GroupPassingTestsDisabledPass rate
Stable1115073%
Tentative000–
Reftests000–
Crash tests000–
All1115073%

Failure reasons

The tests that do not pass (failing or disabled), by kind of reason. A test with several reasons counts once per kind.

  • TEST BUG: 3
  • NOT IMPLEMENTED: 2

Stable tests

TestResultSubtestsKindDescription
detached.https.window.jsTimeout0 / 1TEST BUG, NOT IMPLEMENTEDthe test waits for the messages of the same-origin popups opened by the cross-site and cross-origin frames (same-origin-11, same-origin-13), whose Cross-Origin-Opener-Policy: same-origin response switches them to another browsing context group, which removes their opener (as window-open.mix.https.window.js): the test times out; the realms of the detached frames and of the replaced documents that the scripts keep alive: the measurement only lists the documents of the navigables of the browsing context group
idlharness.window.jsFail4 / 5TEST BUG1 subtest: measureUserAgentSpecificMemory() is declared [CrossOriginIsolated], so it is only exposed when the global object is cross-origin isolated (https://webidl.spec.whatwg.org/#CrossOriginIsolated); the test page has no Cross-Origin-Opener-Policy and Cross-Origin-Embedder-Policy headers, and idlharness.js does not implement [CrossOriginIsolated]: it expects the operation on the prototype of Performance, which Chromium hides too
iframe.cross-origin.https.window.jsPass1 / 1
iframe.cross-site.https.window.jsPass1 / 1
iframe.same-origin.https.window.jsPass1 / 1
main-frame-and-worker.https.window.jsFail0 / 1NOT IMPLEMENTEDthe measurement of the JavaScript heap: the sizes are a deterministic estimate of the objects of the library (a base size per realm, the nodes and the text of the documents), so the 10 MB Uint8Array that the worker allocates is not counted, and bytes is below the 10 MB the test expects
main-frame.https.window.jsPass1 / 1
randomized-breakdown.https.window.jsPass1 / 1
redirect.client.https.window.jsPass1 / 1
redirect.server.https.window.jsPass1 / 1
shared-worker.https.any.jsPass1 / 1
window-open.cross-origin.https.window.jsPass1 / 1
window-open.cross-site.https.window.jsPass1 / 1
window-open.mix.https.window.jsTimeout0 / 1TEST BUGthe test waits for the messages of the same-origin popups opened by the cross-origin frames (same-origin-5, same-origin-7): the initial about:blank document of a popup created by a frame whose origin is not the origin of its top-level document has the unsafe-none opener policy, so the Cross-Origin-Opener-Policy: same-origin response of the popup switches it to another browsing context group (https://html.spec.whatwg.org/multipage/browsers.html#check-browsing-context-group-switch-coop-value), which removes its opener: its messages never reach the frame that opened it, and the test times out
window-open.same-origin.https.window.jsPass1 / 1