1300855 - Add epoch to Memory.jsm

Status: RESOLVED WONTFIX

(Toolkit :: Performance Monitoring, defect)

Description

[Mike Conley (:mconley) (:⚙️)]

Memory.jsm was added in bug 1255843 as an easier to use interface for broadcasting requests for memory summary data from each content process.

It's possible for the parent to time out waiting for a response from each content process, and send out another memory summary request. It's then possible for backlogged summaries from the previous timed out call to arrive and cause the parent to resolve.

We should probably have some kind of "epoch" or "id" in Memory.jsm that gets sent down to each content process. When the content processes respond, they should echo back this epoch / id.

In Memory.jsm, when we receive a memory summary, we should make sure that the epoch is equal to the one we last sent out, otherwise we should ignore it.

Comment 1

[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.