903851 - multipart/x-mixed-replace not freeing memory for replaced images (memory exhaustion)

Status: RESOLVED INCOMPLETE

(Core :: Graphics, defect)

Description

[Bartlomiej Balcerek]

Attachment: server-mozilla.py

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:20.0) Gecko/20100101 Firefox/20.0 (Beta/Release)
Build ID: 20130329042733

Steps to reproduce:

Problem exists while receiving "Content-Type: multipart/x-mixed-replace" data. Example server is attached to reproduce the bug.


Actual results:

Looks like Firefox does not release memory of subsequent content parts. Delivering a number of parts causes memory exhaustion and crash of application or operating system.


Expected results:

A stable operation.

Comment 1

[Matt Wobensmith [:mwobensmith][:matt:]]

After a few minutes, it takes up all system memory - so, confirmed. 

All branches, all platforms. No crash AFAICT.

Comment 2

[Bartlomiej Balcerek]

In fact exhaustion could be done in seconds, by sending much larger pictures. Crash depends on operating system and its configuration. "Crashing" I mean OS kills Firefox or OS becomes irresponsible.

Comment 3

[Daniel Veditz [:dveditz]]

Not sure if this is a document/DOM kind of issue or a graphics memory cache issue, but if we're holding on to images we don't need we should free them.

It won't eliminate the possibilities of DoS attacks though because you could put as many compression-bomb images as you like on a single page to do that.

Comment 4

[Bartlomiej Balcerek]

Will this obvious issue be fixed ? Opera and Chromium browsers are not affected. If you don't consider this a bug, will you concern about making details public in near time ?

Comment 5

[Alin Ilea, Desktop Test Engineering [PTO until Aug 31st]]

Marking this as Resolved > Incomplete since the last activity on this issue was 8 years ago and it might not be relevant anymore. Feel free to re-open if the issue is still reproducible on your end in the latest FF versions.