1177858 - PerformanceStats should offer a memory probe

Status: RESOLVED WONTFIX

(Toolkit :: Performance Monitoring, defect)

Description

[David Teller [:Yoric] - still alive but not very active]

For webpages, use `nsIMemoryReporter::sizeOfTab`.

For compartments, use `JSCompartment::addSizeOfIncludingThis`.

Comment 1

[Gregg Lind (Fx Strategy and Insights - Shield - Heartbeat )]

(my use case is for a toy addon that allows fast filtering, display and killing of high memory pages.  My prefered UI wiould be something like:  

listOfPerformanceObjectsJson <- Services.performance.memoryOfTabs([tabIds?])

)

Comment 2

[David Teller [:Yoric] - still alive but not very active]

That's almost feasible already, in non-e10s mode. See `nsIMemoryReporter::sizeOfTab`. You just need to provide the `nsIDOMWindow` instead of the `tabId`.

Comment 3

[Gregg Lind (Fx Strategy and Insights - Shield - Heartbeat )]

(I am having trouble actually figuring out how to use these apis.  https://developer.mozilla.org/en-US/docs/Mozilla/Tech/XPCOM/Reference/Interface/nsIMemoryReporter.  A js code sample would be awesome.)

Comment 4

[David Teller [:Yoric] - still alive but not very active]

Let's ask the author.

Comment 5

[Nicholas Nethercote [inactive]]

I just searched for "sizeOfTab" on DXR and found two uses, one in test_memoryReporters.xul and one in memory.js. I'd look there. Once you've done that I'm happy to answer more specific questions.

Comment 6

[Florian Quèze [:florian]]

about:performance is being redesigned; mass closing the bugs related to parts of the current about:performance page that we are not keeping.

Our goals with the redesign are to reduce the overhead caused by having the page opened, increase the reliability of the displayed information, and make the offered information actionable for most users. The back-end work is being tracked in bug 1419681.