1370836 - Memory leak while sending jpeg-streams over websocket using FireFox with e10s

Status: UNCONFIRMED

(Core :: DOM: Core & HTML, defect, P3)

Description

[maxim.janzen]

Attachment: memory-report-with-e10s-1.json.gz

User Agent: Mozilla/5.0 (Windows NT 6.3; Win64; x64; rv:53.0) Gecko/20100101 Firefox/53.0
Build ID: 20170518000419

Steps to reproduce:

We are sending jpeg-streams over websocket to our Website, Sadly I cannot provide any source code or test-system for reproducing, but I found a similar bug (Bug 1280916) which seems to be the same issue, also I will attach some memory reports from about:memory. If the time distance they were created is to short for comparison, I will create new reports.


Actual results:

With e10s activated our memory is constantly increasing, with e10s deactivated the memory usage is stable.


Expected results:

The memory usage, using FireFox with e10s, should be stable.

Comment 1

[maxim.janzen]

Attachment: memory-report-with-e10s-2.json.gz

Comment 2

[Andrew Overholt [:overholt]]

baku, please take a look.

Comment 3

[Andrea Marchesini [:baku]]

Hi, sorry for the delay. Do you think it's possible for you to provide a testcase?
I know that firefox has a memory leak (and we are working on it) when websockets are used in workers in non-e10s. Maybe this is connected.

Comment 4

[maxim.janzen]

Hi, I am also sorry for the delay, I will communicate this with my team leader and message you if I have more information.

Comment 5

[maxim.janzen]

I have the ok to provide an test-system for you, but it will take some days to set everything up.

Comment 6

[maxim.janzen]

I have created a virtual machine in azure with our software installed. If its possible I would provide the login data to this machine privately to an responsible official.

Comment 7

[Sylvestre Ledru [:Sylvestre]]

Moving to p3 because no activity for at least 1 year(s).
See https://github.com/mozilla/bug-handling/blob/master/policy/triage-bugzilla.md#how-do-you-triage for more information