Status

()

defect
P3
normal
Last year
4 months ago

People

(Reporter: sebastien.barnoud, Unassigned)

Tracking

60 Branch
Unspecified
macOS
Points:
---

Firefox Tracking Flags

(firefox60 affected, firefox61 affected, firefox62 affected)

Details

Attachments

(7 attachments)

Reporter

Description

Last year
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:60.0) Gecko/20100101 Firefox/60.0
Build ID: 20180605171542

Steps to reproduce:

Go to: https://www.boursorama.com/cours/1rPSOI/

Just wait a while (or refresh sometimes)

Firefox 60.0.2 on MacOSX 10.12.6


Actual results:

Memory growth for ever.
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:62.0) Gecko/20100101 Firefox/62.0 
Build ID:20180612100037      
I manage to reproduce this issue on Mac 10.13 with the latest FF 62.0a1. Here you can see more details about my performance results: https://perfht.ml/2LR2Js1.
Status: UNCONFIRMED → NEW
Component: Untriaged → DOM
Ever confirmed: true
Flags: needinfo?(mconley)
OS: Unspecified → Mac OS X
Product: Firefox → Core
Hi sebastien.barnoud, Daniel_A. I'm unable to reproduce this issue - I've had the site open for about 10 minutes now and memory seems pretty steady.

Daniel_A - if you're able to reproduce this, can you post an about:memory report instead? Gecko Profiler profiles are really only useful when attempting to investigate jank / responsiveness issues with the browser.
Flags: needinfo?(mconley) → needinfo?(daniel.aschilean)
Reporter

Comment 3

Last year
First memory measure
Reporter

Comment 4

Last year
Second memory measure
Reporter

Comment 5

Last year
Third memory measure
Reporter

Comment 6

Last year
I send you 3 memory measure on my current FireFox session. I reload the page several times in between. You should see about 400 MB memory increase (that what's the OS reports to me in the process viewer).
I verified this issue on Mini Mac and MacBook Pro 10.13 with FF 62.0a1 (2018-06-17) the latest version and I cannot reproduce it. Please note that this issue is still reproducible with the old version FF 62.0a1 (2018-06-14) from comment 1.
sebastien.barnoud could you please tell me on what FF version did you test this? If this is on release 60 please download and install FF Nightly 62 and retest this. Here is a link form where you can install Firefox Nightly: https://nightly.mozilla.org
Flags: needinfo?(daniel.aschilean) → needinfo?(sebastien.barnoud)
Reporter

Comment 8

Last year
Hi,

I'm currently running:

60.0.2
Firefox Release

June 6, 2018

Anyway, i experiment the issue since a while.

Regards
Flags: needinfo?(sebastien.barnoud)
Hi Daniel_A,

Could you please gather a memory report from the build that can reproduce the bug, and a memory report from a build where the bug is not present, and then post them to this bug? That should hopefully help me narrow down what (if anything) got fixed here, and we can dupe this over.
Flags: needinfo?(daniel.aschilean)
Reporter

Comment 10

Last year
Actually, Firefox (60.0.2) has 3Gb memory more than yesterday ... So current release produce the pb at least for me.

I have uploaded a new memory report

Regards
Reporter

Comment 12

Last year
A screen shot of process monitor showing the OS point of view on memory usage.
Posted file memory-report.json
Here you have the memory report where the bug is present on Mac 10.12 FF 62.0a1(2018-06-14):
Flags: needinfo?(daniel.aschilean)
And memory report from build where the bug is not present on FF 62.0a1 (2018-06-19):
Priority: -- → P3
Component: DOM → DOM: Core & HTML
You need to log in before you can comment on or make changes to this bug.