[webkit-dev] Feedback on the performance.measureMemory API proposal

Ulan Degenbaev ulan at google.com
Thu Apr 2 05:17:12 PDT 2020

Hello webkit-dev,

I'd like to solicit feedback as well as an official position from Webkit on
our proposal for the new memory measurement API:

The proposal generalizes the previous performance-memory proposal [1] that
was abandoned [2] due to information leak of cross-origin resources. The
new API addresses the information leak and process model issues raised in
the previous feedback [3].

What is different in the new API?

- It relies on COOP+COEP [4] for preventing cross-origin information leaks
(see "Security Considerations"). Besides security, COOP+COEP also helps
implementability because the browser needs to isolate the web page from
other web pages.
- It does not assume any particular process model and is defined using the
standard concepts such as JS agent cluster and browsing context group.
- It has an extensible and generic interface for breaking down memory usage
by type (JS, DOM, GPU) and owner. Implementers can choose the level of
detail they are willing to provide based on their performance trade-offs
(see "Performance Considerations").

Thank you,

[1]: The previous proposal:
[2]: Information leak affecting the previous proposal:
[3]: Feedback from Apple on the previous proposal:
[4]: COOP and COEP explained:

Other Relevant Links

Explainer: https://github.com/WICG/performance-measure-memory
Open issues: https://github.com/WICG/performance-measure-memory/issues
WebPerf WG F2F June 2019 presentation (for older iteration of the API):
TAG design review (for older iteration of the API):
Issue on Mozilla standards-positions:
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-dev/attachments/20200402/43a0f528/attachment.htm>

More information about the webkit-dev mailing list