Implement memory reporter for Gloda. xref Bug 472209 which begins implementing reporters for core
I think this is probably moot now that one-compartment-per-global has landed. If you go to "Help", "Troubleshooting Information", "about:memory", then hit "more verbose" at the bottom, you can see all of gloda's module's memory usage. Specifically, look for compartments with URLs that look like: - resource:///modules/gloda/*.js - file:///.../components/jsmimeemitter.js The JS mime emitter and mimemsg.js are going to incur the costs of all message streaming which covers gloda's indexing efforts, the multi-message summaries, some of Thunderbird Conversation's display stuff (I think?), and I think even enigmail uses the API.
You need to log in before you can comment on or make changes to this bug.