SummerOfCode/2013/newMemoryPage/week5

End of Week 5: Report

Roadblock. Having addressed the problem of data polling in the second week, I did not think I would have to look into it again. But, it would seem that the actual 'tab-data' is missing from our current data-set. It turns out that the memory reporters come in two flavors -- the 'single' memory reporters, and 'multi' memory reporters. It has generally been agreed that this project should be useful to web developers, and for it to do that, it must address the individual tabs in a separate visualization.

Unfortunately, we have only been working with the single reporters, and they did not contain that data. Even after a great deal of effort, I could not extract the necessary hierarchical structure from these multi-reporters. That is when my mentor stepped in and showed me how to design a dedicated multi-reporter-enumerator method (see it here).

EDIT: Although this did take up valuable time, the lesson was important because as of Nightly 27, Firefox has decided to do away with the separate reporter objects, and single reporters will be removed with their data made accessible through the common reporter object nsImemoryReporter, which is the old multi-reporter.