Open Bug 1358285 Opened 7 years ago Updated 2 years ago

Would be nice if MemoryBlobImplDataOwnerMemoryReporter can report the file's origin

Categories

(Core :: DOM: File, enhancement, P3)

Product:
Core
Component:
DOM: File
Type:
enhancement

Tracking

()

Tracking Flags:
Tracking Status
firefox55 --- affected

People

(Reporter: kanru, Unassigned)

Details

(Whiteboard: [MemShrink:P2]) 

Currently I'm looking at about:memory like this:

2,841.44 MB (100.0%) -- explicit
├──1,245.03 MB (43.82%) -- dom
│  ├──1,243.51 MB (43.76%) -- memory-file-data
│  │  ├──1,070.70 MB (37.68%) -- large
│  │  │  ├────528.62 MB (18.60%) ── file(length=5469, sha1=52b8ee960c135b328c564a21d2fa86182c6f84cd) [67663]
│  │  │  ├────324.13 MB (11.41%) ++ (2299 tiny)
│  │  │  ├─────52.94 MB (01.86%) ── file(length=4492, sha1=9216cde2293c630432f143723afaa8acc18af116) [6776]
│  │  │  ├─────51.32 MB (01.81%) ── file(length=8326, sha1=c84eb25adf5a2062cc88b3b0bf6fc04f5995072a) [4379]
│  │  │  ├─────40.81 MB (01.44%) ── file(length=5759, sha1=8a75372013fe7d9f1fc6d7acc8cd674fb8ac8050) [5224]
│  │  │  ├─────40.02 MB (01.41%) ── file(length=4671, sha1=3288f905b1d38bfa30c43af4f4801bf74efa30bc) [5122]
│  │  │  └─────32.88 MB (01.16%) ── file(length=4690, sha1=008b8c86b13828e6c2e5f0c142c4d27a6833d8de) [4208]
│  │  └────172.81 MB (06.08%) ── small
│  └──────1.52 MB (00.05%) ++ (2 tiny)

I don't think the sha1 are very useful unless I can link them to origins in about:memory.

It would nice to know which domain the blobs are coming from.
The leak itself might be bug 1272078
Priority: -- → P3
Whiteboard: [MemShrink]
kanru, are you still seeing this after bug 1272078 landed?
Flags: needinfo?(kchen)
Whiteboard: [MemShrink] → [MemShrink:P2]
Looks like the leak is gone. I can't find any memory-file-data in about:memory anymore.
Flags: needinfo?(kchen)
It can be a side effect of the IPCBlob refactoring.
Component: DOM → DOM: File
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.