large compartment for nsLivemarkService.js

NEW
Unassigned

Status

()

Toolkit
Places
P3
normal
5 years ago
7 months ago

People

(Reporter: mak, Unassigned)

Tracking

Trunk
x86_64
Windows 7
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [MemShrink:P3])

(Reporter)

Description

5 years ago
Not sure if there's a leak involved, or just result of the caching, but I see this in my about:memory

─6.36 MB (01.89%) -- compartment([System Principal], jar:file:///C:/Program%20Files%20(x86)/Mozilla%20Firefox/omni.ja!/components/nsLivemarkService.js)
│  │  │   │   ├──4.37 MB (01.30%) -- gc-heap
│  │  │   │   │  ├──2.23 MB (00.66%) ++ shapes
│  │  │   │   │  ├──1.80 MB (00.53%) ++ objects
│  │  │   │   │  ├──0.22 MB (00.07%) ── unused-gc-things
│  │  │   │   │  ├──0.05 MB (00.01%) ── type-objects
│  │  │   │   │  ├──0.03 MB (00.01%) ── arena-admin
│  │  │   │   │  ├──0.02 MB (00.01%) ── strings/normal
│  │  │   │   │  ├──0.01 MB (00.00%) ── scripts
│  │  │   │   │  └──0.01 MB (00.00%) ── sundries
│  │  │   │   └──2.00 MB (00.59%) -- (6 tiny)
│  │  │   │      ├──1.64 MB (00.49%) ++ shapes-extra
│  │  │   │      ├──0.13 MB (00.04%) ── cross-compartment-wrapper-table
│  │  │   │      ├──0.11 MB (00.03%) ++ objects-extra
│  │  │   │      ├──0.09 MB (00.03%) ── string-chars/non-huge
│  │  │   │      ├──0.02 MB (00.01%) ── script-data
│  │  │   │      └──0.00 MB (00.00%) ── other-sundries
(Reporter)

Comment 1

5 years ago
fwiw, I have about 25 livemarks
(Reporter)

Updated

5 years ago
Blocks: 692748
Whiteboard: [MemShrink]
And note that in bug 692748, one user saw the nsLivemarkService.js compartment grow from 1,836,488 bytes to 20,847,464 bytes during 10 hours of idleness.

Bug 692748 comment 32 has the full analysis.
(Reporter)

Comment 3

5 years ago
I must point my finger to the feedProcessor. But we also cache some objects (not that many).
It's quite good the issue is reproducible so we can actually test improvements.
Whiteboard: [MemShrink] → [MemShrink:P3]
(Reporter)

Updated

7 months ago
Priority: -- → P3
You need to log in before you can comment on or make changes to this bug.