Closed
Bug 106792
Opened 24 years ago
Closed 22 years ago
remove nsISizeOfHandler
Categories
(Core :: XPCOM, defect, P1)
Core
XPCOM
Tracking
()
RESOLVED
FIXED
Future
People
(Reporter: dbaron, Assigned: dbaron)
Details
(Whiteboard: [patch])
Attachments
(1 file, 1 obsolete file)
316.63 KB,
patch
|
bzbarsky
:
review+
jst
:
superreview+
|
Details | Diff | Splinter Review |
We should remove nsIAtom::SizeOf. Any debugging code that's using it is
probably way over-accounting for the atoms anyway, since they're shared. That's
why trace-malloc and friends are better.
Assignee | ||
Updated•23 years ago
|
Status: NEW → ASSIGNED
Comment 1•23 years ago
|
||
Can we also get rid of nsISizeOfHandler?
Assignee | ||
Comment 2•23 years ago
|
||
I'd *love* to (since modifying layout data structures always requires spending
double the time modifying the SizeOf methods), but attinasi seems to think that
people still use it and wants it to stay (at least when I asked back in July),
although maybe we should be evangelizing trace-malloc more.
Assignee | ||
Updated•23 years ago
|
Priority: -- → P1
Target Milestone: --- → Future
Assignee | ||
Comment 3•22 years ago
|
||
OK, changing this bug into being on removing nsISizeOfHandler. trace-malloc is
far better (especially since it doesn't contain bias introduced by programmer
error in writing SizeOf methods) and requires no code maintainance.
Any objections?
Summary: remove nsIAtom::SizeOf → remove nsISizeOfHandler
Assignee | ||
Updated•22 years ago
|
Whiteboard: [patch]
Assignee | ||
Comment 4•22 years ago
|
||
Assignee | ||
Comment 5•22 years ago
|
||
cc:ing a few more people to see if they care about nsISizeOfHandler.
The one objection I heard is from Bernd, who suggested that nsISizeOfHandler is
an easier way to see how much a specific change helped. However, I'd think you
could easily figure that out (if you really need accurate numbers) using a
printf printing the sizeof() of the object and a simple counter (just find the
max of a static gInstanceCnt variable) to see how many instances of the object
were created at one time. In most cases I'd think approximate numbers for that
kind of thing are good enough, though.
Comment 6•22 years ago
|
||
I say kill it, Kill it, KILL IT! IMO nsISizeOfHandler is useless since most
people (me included) don't take the time to make sure it does the right thing
when making changes to classes, and I don't think that'll change...
as I wrote in my email my objection was a recall what Marc said and I have no
interest in keeping it.
Comment 9•22 years ago
|
||
dbaron, do you see any footprint savings?
Assignee | ||
Comment 10•22 years ago
|
||
It's practically all debug code.
Assignee | ||
Updated•22 years ago
|
Attachment #113300 -
Flags: superreview?(jst)
Attachment #113300 -
Flags: review?(bzbarsky)
![]() |
||
Comment 11•22 years ago
|
||
Comment on attachment 113300 [details] [diff] [review]
patch
Ah, the smell of fresh code removal on a Saturday morning... it warms the
heart. ;)
Attachment #113300 -
Flags: review?(bzbarsky) → review+
Comment 12•22 years ago
|
||
Comment on attachment 113300 [details] [diff] [review]
patch
<smile size='huge'>
sr=jst
</smile>
:-)
Attachment #113300 -
Flags: superreview?(jst) → superreview+
Assignee | ||
Comment 13•22 years ago
|
||
Fix checked in to trunk, 2003-02-22 07:34 PST (with dlldeps.cpp later).
Status: ASSIGNED → RESOLVED
Closed: 22 years ago
Resolution: --- → FIXED
Comment 14•22 years ago
|
||
I hate to bring this up, but wasn't nsIAtom frozen?
Assignee | ||
Comment 15•22 years ago
|
||
It's not marked frozen, and it needs other changes before it is (it shouldn't be
scriptable, since wrapping can break it).
Comment 16•22 years ago
|
||
sorry my bad.. I could have SWORN this was frozen..
You need to log in
before you can comment on or make changes to this bug.
Description
•