The default bug view has changed. See this FAQ.

"explicit/atoms-table" reporter always returns 0

RESOLVED FIXED in Firefox 18

Status

()

Core
XPCOM
RESOLVED FIXED
4 years ago
4 years ago

People

(Reporter: njn, Assigned: njn)

Tracking

(Blocks: 1 bug)

unspecified
mozilla19
x86_64
Linux
Points:
---

Firefox Tracking Flags

(firefox18 fixed, firefox19 fixed)

Details

(Whiteboard: [MemShrink])

Attachments

(1 attachment)

(Assignee)

Description

4 years ago
"explicit/atoms-table" reporter always returns 0, due to a stupid and trivial defect.
(Assignee)

Comment 1

4 years ago
Created attachment 680010 [details] [diff] [review]
Fix stupid defect causing the "explicit/atoms-table" reporter to always return 0.

Trivial fix.
Attachment #680010 - Flags: review?(khuey)
Comment on attachment 680010 [details] [diff] [review]
Fix stupid defect causing the "explicit/atoms-table" reporter to always return 0.

Review of attachment 680010 [details] [diff] [review]:
-----------------------------------------------------------------

ha
Attachment #680010 - Flags: review?(khuey) → review+
Comment on attachment 680010 [details] [diff] [review]
Fix stupid defect causing the "explicit/atoms-table" reporter to always return 0.

Simple memory reporter fix; a-a+ if you want it.
Attachment #680010 - Flags: approval-mozilla-aurora+
(Assignee)

Comment 4

4 years ago
https://hg.mozilla.org/integration/mozilla-inbound/rev/1ac4c8b22172

> Simple memory reporter fix; a-a+ if you want it.

Yes please.  On b2g-desktop64 I'm seeing sizes of 300--500 KiB per-process on startup, which is up to 2.5% of "explicit".  So this is a big missing chunk.
https://hg.mozilla.org/mozilla-central/rev/1ac4c8b22172
Status: ASSIGNED → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla19
https://hg.mozilla.org/releases/mozilla-aurora/rev/eff0efa2ae52
status-firefox18: --- → fixed
status-firefox19: --- → fixed
You need to log in before you can comment on or make changes to this bug.