Open
Bug 1016445
Opened 10 years ago
Updated 2 years ago
nsAppShellService created (hidden?) windows fail to report allocated memory that other windows report
Categories
(Core :: General, defect)
Tracking
()
NEW
People
(Reporter: jwatt, Unassigned)
References
(Blocks 2 open bugs)
Details
Attachments
(2 files)
If I add reporting of PresShell's nsFrameSelection member (mSelection) then the DMD stacks showing the nsFrameSelection ctor being called from PresShell::Init move from the Unreported to the Once-reported section of DMD's reports...except if the PresShell is created under nsAppShellService::JustCreateTopWindow. Perhaps nsWindowMemoryReporter::CollectReports needs to do something special for these windows?
![]() |
Reporter | |
Comment 1•10 years ago
|
||
![]() |
Reporter | |
Comment 2•10 years ago
|
||
![]() |
Reporter | |
Comment 3•10 years ago
|
||
(In reply to Jonathan Watt [:jwatt] from comment #2) > Created attachment 8429377 [details] > the four post-patch DMD stacks Hmm, the fourth stack isn't relevant actually. Not sure why we went from four to three relevant stacks. I'll redo the measurements.
![]() |
Reporter | |
Comment 4•10 years ago
|
||
I now can't reproduce this, but I'm pretty sure I'm doing the same thing as before. Maybe there's some non-determinism somewhere?
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•