1547912 - Memory Issue on oilprice.com, reuters.com

Status: REOPENED

(Core :: Memory Allocator, defect, P5)

Description

[bht237]

On the oilprice.com home page, and on the page https://oilprice.com/Geopolitics/Middle-East/A-New-Middle-East-Mega-War-Is-Unfolding-Right-Before-Our-Eyes.html the browser quickly consumes excessive amounts of memory such as more than 1GByte.

Comment 1

[Anthony Jones (:ajones, :kentuckyfriedtakahe, :k17e)]

Attachment: memory-report.json.gz

I'm seeing the content process using 129MB. Can you please take a snapshot from about:memory on your system?

Comment 2

[Eric Rahm [:erahm]]

Lets close this for now, feel free to reopen if you can reproduce the issue.

Comment 3

[bht237]

When opening
https://www.reuters.com/article/us-nuclearpower-uranium-cameco/cameco-may-cut-uranium-output-further-as-demand-stalls-idUSKCN1VQ2GD

then memory grows at a rate of 100MB per minute. Good way to get rid of all Firefox browsers on the planet.

I have a script that kills each firefox process at above 1GB so it is easy for me to spot the culprit before my Windows system becomes totally unusable and needs to be re-started WITH THE POWER BUTTON.

I have never in my life (and I am using browsers since Netscape 1) seen any software that would do this to my system.

And here is the proof that I am one of the last die-hard users left:

while ($true) {
Get-Process firefox -ea 0 | where { $.PM -ge 1000MB } | foreach {
[bool]$Ping = Test-Connection 8.8.8.8 -Quiet
if ($Ping) {
##### write-host $ # System.Diagnostics.Process (firefox)
##### write-host $.ID
Stop-Process $.ID -Force
}
}
sleep -s 1
}

So, we actually have two problems:

1. Memory usage grows
2. Memory usage grows without bounds to the extent that the browser crashes the OS.

The browser is too stupid to limit its resource use. I have multiple software packages running simultaneously each of them exits gracefully under user control when memory usage gets beyond pre-set limits.

And these packages are running on the JVM (Java software)! Banned by Firefox. Remember? Now it is ECMAScript which causes the headaches. Far worse.