Closed Bug 1152582 Opened 9 years ago Closed 9 years ago

very high ftp:// memory consumption (resource exhaustion)

Categories

(Core :: Graphics: ImageLib, defect)

37 Branch
x86
All
defect
Not set
critical

Tracking

()

RESOLVED DUPLICATE of bug 1148682

People

(Reporter: mancha1, Unassigned)

References

()

Details

(Whiteboard: [MemShrink])

Firefox 37.0.1 memory consumption spikes to over 3GB when loading/rendering ftp://ftp.vim.org/pub/vim/patches/7.4 (images->content/raster/used->source). CPU usage also spikes. Behavior borders on being a resource exhaustion DoS.

Firefox 36.0.4 renders without issues.

Tests done on new installs with vanilla profiles (i.e. no 3rd party extensions/plugins)

=======
Explicit Allocations

3,275.28 MB (100.0%) -- explicit
├──3,129.10 MB (95.54%) -- images
│  ├──3,128.23 MB (95.51%) ++ content/raster/used
│  └──────0.87 MB (00.03%) ++ (2 tiny)
├─────95.46 MB (02.91%) ++ (24 tiny)
└─────50.72 MB (01.55%) ++ js-non-window

3,129.10 MB (100.0%) -- images
├──3,128.23 MB (99.97%) -- content/raster/used
│  ├──3,128.22 MB (99.97%) ── source
│  └──────0.01 MB (00.00%) ── decoded-heap
└──────0.87 MB (00.03%) ++ (2 tiny)
I'm not seeing that behavior on Firefox 40.  It seems odd that there's so much memory being used for images just to display an FTP screen.  Does it show any kind of images on the screen besides the little file icons?
Component: General → ImageLib
Product: Firefox → Core
Whiteboard: [MemShrink]
Fixed in 38 already.
Status: UNCONFIRMED → RESOLVED
Closed: 9 years ago
Resolution: --- → DUPLICATE
Thanks for the reply - I wouldn't have found bug 1148682 on my own.

According to some quick googling, FF 38 is due out 2015-05-12. Does that mean we'll see the fix back-ported to 37?
(In reply to mancha from comment #3)
> Thanks for the reply - I wouldn't have found bug 1148682 on my own.
> 
> According to some quick googling, FF 38 is due out 2015-05-12. Does that
> mean we'll see the fix back-ported to 37?

Unfortunately not; the fix for bug 1148682 came too late to make it into the FF 37 release. Sorry about that. =(

FF 38 is available as Firefox Beta right now, so you can use it today if you'd like.
(In reply to Seth Fowler [:seth] from comment #4)
> Unfortunately not; the fix for bug 1148682 came too late to make it into the
> FF 37 release. Sorry about that. =(
> 
> FF 38 is available as Firefox Beta right now, so you can use it today if
> you'd like.

Thanks. I actually meant 37.0.2 (or so) though back-ports are probably limited to egregious blockers and/or bugs with likely security implications.
Thanks for the report!  We happened to have caught this one ourselves but there are plenty of memory issues that only happen some times and are hard to figure out without reports.
You need to log in before you can comment on or make changes to this bug.