Open Bug 1563745 Opened 6 years ago Updated 3 years ago

Large amount of unclassified memory when viewing amazon.com/photos

Categories

(Core :: Graphics, defect, P3)

defect

Tracking

()

Tracking Status
firefox69 --- affected

People

(Reporter: jesup, Unassigned)

References

()

Details

(Whiteboard: [MemShrink:P2][sci-exclude])

(Could be DOM instead of gfx)

Web Content (pid 18368)
Explicit Allocations

2,498.64 MB (100.0%) -- explicit
2,286.32 MB (91.50%) ?? heap-unclassified
??????74.98 MB (03.00%) -- window-objects
? ???42.55 MB (01.70%) ++ (4 tiny)
? ???32.42 MB (01.30%) ++ top(https://www.amazon.com/photos/all, id=<redacted>)

The 4 tiny were a woot.com cart, a ghost window from quora.com, a signin page, and another login page, so I'm betting on amazon photos (I have a lot).

DMD probably would find this fast

closing the amazon window and minimizing memory made it all go away

If I remember correctly, the image data can be shared, and if it is shared, then we don't report it.

There are a bunch of gfx- and imagelib- reports at the bottom of each process's subreport that might help, or of course DMD should also reveal what is going on.

Flags: needinfo?(rjesup)
Whiteboard: [memshrink] → [MemShrink:P2]
Priority: -- → P3
Whiteboard: [MemShrink:P2] → [MemShrink:P2][sci-exclude]
Flags: needinfo?(rjesup)
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.