fix memory reporting in nsMsgDatabase.cpp after removal of NS_RegisterMemoryReporter in bug 936964
Categories
(MailNews Core :: Database, defect)
Tracking
(Not tracked)
People
(Reporter: aceman, Unassigned)
References
(Regression)
Details
(Keywords: regression)
Attachments
(1 file)
(deleted),
patch
|
Details | Diff | Splinter Review |
Comment 2•11 years ago
|
||
Comment 4•11 years ago
|
||
Updated•10 years ago
|
Comment 5•8 years ago
|
||
Comment 6•7 years ago
|
||
Comment 7•7 years ago
|
||
Updated•6 years ago
|
Comment 9•5 years ago
|
||
At this point I agree we should close this as fixed by the bustage patch, and do any "proper" fixing and followup in new bugs. So the remaining questions ...
(In reply to Joshua Cranmer [:jcranmer] from comment #2)
Adopting the not-creating-singletons is still a worthwhile patch, though.
a) Did bug 936964 resolve this?
(In reply to neil@parkwaycc.co.uk from comment #4)
Another approach is to move memory reporting to the nsMsgDBService, although
that would probably require moving the nsMsgDatabase cache there too.
b) Even if other issues have been resolved, from code organization, stability and maintenance POV, is there value in doing this?
c) does the above help us move toward resolving bug 805023 and bug 857373 ?
Comment 10•5 years ago
|
||
It's been so long since those landed and so much has changed since that it's quite hard to say how it impacted at the time or what the status is now.
Description
•