Feedback on the performance.measureMemory API proposal

# Ulan Degenbaev (5 hours ago)

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: WICG/performance-measure-memory

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, Ulan.

[1]: The previous proposal: WICG/performance-memory/blob/master/ [2]: Information leak affecting the previous proposal: mozilla/standards-positions#85 [3]: Feedback from Apple on the previous proposal: WICG/performance-memory#14 [4]: COOP and COEP explained:

Other Relevant Links

Explainer: WICG/performance-measure-memory Open issues: 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): w3ctag/design-reviews#386 Issue on Mozilla standards-positions: mozilla/standards-positions#281

Contact us to advertise here

Want more features?

Request early access to our private beta of readable email premium.