This issue is merely to make it possible to find out about this member by searching this issue tracker.
console.memory is available in Chrome (but not Node.js) and has is an object with totalJSHeapSize, usedJSHeapSize and jsHeapSizeLimit members, just like performance.memory. That's not on a track to standardization, and will be superseded by https://wicg.github.io/performance-measure-memory/.
Why Chrome has both console.memory and performance.memory I don't know, but there you go.
In the spirit of https://github.com/whatwg/console/issues/27 and https://github.com/whatwg/console/issues/74 I'm filing issues about two additional console members I've spotted as part of https://github.com/foolip/mdn-bcd-collector/issues/917.
This issue is merely to make it possible to find out about this member by searching this issue tracker.
console.memoryis available in Chrome (but not Node.js) and has is an object withtotalJSHeapSize,usedJSHeapSizeandjsHeapSizeLimitmembers, just likeperformance.memory. That's not on a track to standardization, and will be superseded by https://wicg.github.io/performance-measure-memory/.Why Chrome has both
console.memoryandperformance.memoryI don't know, but there you go.