A few days ago, I wondered if any of the current “XPCOM objects created/destroyed from static ctor/dtor” warnings were caused by MailNews. A bit of digging later and I filed bug 424677 – nsImapProtocol.cpp had the only warning that came from MailNews; I checked in the fix a few hours ago.
It just so happens that the fix I checked in for the static object was additionally the fix for the last 4 bytes that the Rlk test on the SeaMonkey tinderboxes had been showing for quite a while. This is no where near a major leak fix, and although will still do leak (as per the newer Lk test), it is really satisfying to have at least one of the numbers at zero.
I’d like to note that the main part of reducing Rlk was done by Firefox, who last August, got its Rlk figure down to 0 bytes. Their work on reducing leaks in the core code has helped benefit everyone – I just happened to find the last bit for MailNews/SeaMonkey.