Reflow bugs make refcnt balancer unusable

VERIFIED INVALID

Status

()

P3
normal
VERIFIED INVALID
19 years ago
19 years ago

People

(Reporter: blizzard, Assigned: troy)

Tracking

Trunk
x86
Linux
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

19 years ago
Some reflow bugs in the layout engine make trying to trace refcnt changes on the
nsWidget class almost completely unusable.

Try setting this:

export XPCOM_MEM_REFCNT_LOG=mem.log
export XPCOM_MEM_LOG_CLASSES=nsWidget

and then fire up the browser.  Oh, before you try this make sure that you have
serveral hundred meg of space available.

You can see all the refcnts being added to the window class in the reflow code.
(Assignee)

Updated

19 years ago
Status: NEW → RESOLVED
Last Resolved: 19 years ago
Resolution: --- → INVALID
(Assignee)

Comment 1

19 years ago
I you want the bug looked at then please provide some specifics on which layout
classes are at fault. There are many many frame classes and at least six
different people who own the various sub-modules

Comment 2

19 years ago
Based on troy's comments, marking as verified invalid.
Status: RESOLVED → VERIFIED

Comment 3

19 years ago
blizzard: don't -ever- try to trace every nsWidget in the product. You will
die. Instead, do this:

setenv XPCOM_MEM_BLOAT_LOG /tmp/bloat.log
setenv XPCOM_MEM_LOG_CLASSES nsWidget

Run. You'll get a list of nsWidget object "serial numbers" that leak at the end
of the bloat log. Pick one.

setenv XPCOM_MEM_LOG_CLASSES 93 ### or whatever
setenv XPCOM_MEM_REFCNT_LOG /tmp/refcnt.log

Rerun. You will just get stack traces for the object with serial number 93.
(Reporter)

Comment 4

19 years ago
Ok, I'll keep that in mind.  Thanks.
You need to log in before you can comment on or make changes to this bug.