Memory leak in Isolated Web Co process
Categories
(Core :: Graphics, defect)
Tracking
()
People
(Reporter: baladoramiro+github, Unassigned)
References
Details
Attachments
(5 files)
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:89.0) Gecko/20100101 Firefox/89.0
Steps to reproduce:
The increase in memory usually happens when watching youtube videos.
Actual results:
The used memory of the process called Isolated Web Co quickly starts to grow. When it runs out of physical memory, it continues until all the swap is also consumed
Expected results:
The memory consumption should remain stable.
Reporter | ||
Comment 1•3 years ago
|
||
Reporter | ||
Comment 2•3 years ago
|
||
I am attaching a memory dump that was taken while the process was consuming a lot of memory. It seems that it does not show the process that is responsible for the memory growth though.
Comment 3•3 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'Core::Graphics' component, and is moving the bug to that component. Please revert this change in case you think the bot is wrong.
Reporter | ||
Comment 4•3 years ago
|
||
I forgot to mention that this has been happening roughly once every day or two. It is not clear to me exactly why this happens, but it's always happened when a youtube video was playing, so I'm inclined to think it might be something to do with that.
Reporter | ||
Comment 5•3 years ago
|
||
It happened today once more. This time it did not reach the full memory. Instead after a few seconds the memory was released all at once, without degrading the responsiveness of the system.
Comment 6•2 years ago
|
||
Could you please test this with the current release and see if the behavior still exists?
Reporter | ||
Comment 7•2 years ago
|
||
I have not experienced this bug in several months. From my side I would consider it closed.
Reporter | ||
Comment 8•2 years ago
|
||
I forgot to say that I am currently in version 99.0a1, but it's been a couple of nightly releases that I haven't experienced it, so the bug must have resolved itself somewhere before version 98.
Comment 9•2 years ago
|
||
Please open about:support, click on "Copy text to clipboard" and paste it here.
In case you had manually enabled VAAPI,
- this could have been bug 1743750.
- You might even no longer be using VAAPI because
- your prefs might be messed up (bug 1743647=VAAPI now requires the RDD process: just reset all media prefs back to their default and only set media.ffmpeg.vaapi.enabled=true) or
- you haven't set the MOZ_DISABLE_RDD_SANDBOX=1 environment variable: bug 1751363
Comment 10•2 years ago
|
||
I had a similar issue on Windows in bug 1696827 that was also fixed a few months ago, so I don't know if this is necessarily a Linux-only issue.
Comment 11•2 years ago
|
||
Comment 12•2 years ago
|
||
Memory Leak form isolated web co in firefox for linux
it uses gradually all the ram of the system and then is crashes.
Comment 13•1 year ago
|
||
Still seems to be an issue in 111.0.1 (64-bit) in Linux Mint.
I've created a hot key combo on mint to bring up the system monitor. When I see large amounts of disk activity and slow or no response I bring up the monitor and look as swap in the resources tab. Then I can switch to processes and sort by memory and this process is the culprit. Firefox shutdown of all windows and restart is my current work around along with a big increase in my swap file size to I have time enough to deal with it.
Comment 14•1 year ago
|
||
Hello everyone,
I'd like to add, that it also happens to me.
I'm using Linux Mint 21.1 MATE 64-bit, it happens since I use this version on my main machine.
When there's no RAM available anymore, the system just loads a new session and kills the previous one.
This didn't happen with previous versions (of Linux Mint). All it did was to freeze the machine for some time and either let me continue or at least killed some applications, instead of making me lose everything else that was open.
What I'm running is Mozilla Firefox for Linux Mint mint-001 1.0 (114.0.2 64-bit).
I even went as far as using 128GB RAM (4 x 32GB) and 8GB of SWAP. But this seems not to be enough, for this reason called OOM Killer?
I'm going to increase the SWAP to 16GB now, as I cannot add additional physical RAM anymore.
The syslog lines, that appear highly responsible to this below:
Jul 16 03:17:58 linux-desktop org.mate.panel.applet.MintMenuAppletFactory[77942]: #033[93m[main 2023-07-16T00:17:57.928Z]#033[0m No ptyHost heartbeat after 6 seconds
Jul 16 03:19:15 linux-desktop kernel: [573290.035892] Isolated Web Co invoked oom-killer: gfp_mask=0x1100cca(GFP_HIGHUSER_MOVABLE), order=0, oom_score_adj=100
Jul 16 03:19:15 linux-desktop kernel: [573290.037345] oom-kill:constraint=CONSTRAINT_NONE,nodemask=(null),cpuset=/,mems_allowed=0,global_oom,task_memcg=/user.slice/user-1000.slice/user@1000.service/app.slice/dbus.service,task=steamwebhelper,pid=1002275,uid=1000
Jul 16 03:19:15 linux-desktop kernel: [573290.037377] Out of memory: Killed process 1002275 (steamwebhelper) total-vm:5378480kB, anon-rss:457332kB, file-rss:0kB, shmem-rss:236468kB, UID:1000 pgtables:4312kB oom_score_adj:300
Comment 15•7 months ago
|
||
I am using several Discourse forums, and often I have a number of tabs open. Each one creates an Isolated Web Co, which I can see using "ps auxc | grep Isolat".
However, after I close my Discourse tabs, the associated Isolated Web Co processes do not go away. Same thing for youtube videos.
I have to close Firefox to make them go away, and if I run up enough of them, they bog my system down -- there's a noticeable improvement to the system speed if I close Firefox and restart it, anyways, and if I'm not one a Discourse or video binge, I don't see that slowdown.
I am running Fedora Linux on an older laptop with 8G memory.
Comment 16•7 months ago
•
|
||
I just tested on Ubuntu 22.04 LTS using Fx120.0.1 by opening several YT video tabs, checking (using ps auxc | grep Isolat
) and then closing the tabs and checking again. The associated Isolated Web Co
processes go away for me. I'm left with one isolated Web Co
process per remaining tab.
Comment 17•5 months ago
|
||
(In reply to yosora21 from comment #12)
Memory Leak form isolated web co in firefox for linux
it uses gradually all the ram of the system and then is crashes.
I'm having the same problem in snap Firefox in Ubuntu 22.04. I have 32 gb RAM and 40 gb swap, so it takes a long time before it takes up all my memory, but it always eventually manages to fill it up. I do use a lot of tabs, but ideally I would like to be able to keep my computer running with Firefox open indefinitely without having to restart either the computer or Firefox. I think most of these "Isolated Web Co" processes are YouTube-related, so I was thinking maybe the solution is just to run YouTube in Chrome. Ideally, I'd like to figure out how to track down each "Isolated Web Co" process and kill it individually when it happens, or maybe write a script that will identify the tab responsible for the memory leak. The GNOME task manager can find the worst offending processes, but it seems like killing them freezes the whole FireFox app, rather than just that tab.
(In reply to Bob Hood [:bhood] from comment #16)
I just tested on Ubuntu 22.04 LTS using Fx120.0.1 by opening several YT video tabs, checking (using
ps auxc | grep Isolat
) and then closing the tabs and checking again. The associatedIsolated Web Co
processes go away for me. I'm left with oneisolated Web Co
process per remaining tab.
I tried the same thing with some YouTube tabs. Can confirm. However, I still have about 60-80 "Isolated Web Co" processes running. I guess what I really need is a way to track down each one and find out what it's doing. It definitely seems like the memory usage reported in about:processes doesn't line up with what the system sees in gnome system monitor
Description
•