[webkit-dev] Moving MemoryInfo under window.internals
zandobersek at gmail.com
Tue May 28 13:27:17 PDT 2013
the MemoryInfo interface is currently exposed in window.console and
window.performace despite not being standardized or in process of
standardization by any spec. It's also only partially functional under the
JSC bindings as the jsHeapSizeLimit attribute returns an undefined value.
At the moment grepping through the source tree only shows two uses of the
interface in a couple of PerformanceTests files. Is anyone else aware
of any other places where it's used downstream (so its removal would break
things outside of WebKit)?
If possible, I propose moving the interface under window.internals and
adjust the two places where it's used. This also opens the possibility of
removing two MemoryInfo-specific settings, memoryInfoEnabled and
quantizedMemoryInfoEnabled. The quantization of the given memory
information is also not necessary anymore as the information is not exposed
to the Web anymore.
The jsHeapSizeLimit attribute should be removed as well as it's basically a
no-op with the JSC bindings.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the webkit-dev