Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.user > #264307

Re: Isolated Web Co Session crash Firefox-ESR

From jeremy ardley <jeremy.ardley@gmail.com>
Newsgroups linux.debian.user
Subject Re: Isolated Web Co Session crash Firefox-ESR
Date 2023-12-05 19:50 +0100
Message-ID <HHIEx-bsNW-1@gated-at.bofh.it> (permalink)
References <HGMKd-aInC-1@gated-at.bofh.it> <HGNPX-aJkB-11@gated-at.bofh.it> <HGOiZ-aJtY-1@gated-at.bofh.it> <HH6SB-aURe-1@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


On 4/12/23 10:26, Max Nikulin wrote:
> On 03/12/2023 13:33, jeremy ardley wrote:
>> On 3/12/23 13:59, Phil Wyett wrote:
>>> What type of content is generally being viewed/used in firefox?
>>
>> A lot of video and otherwise news and search and GPT4
> ---------------------------------------------------^^^^
>
> I am curious if this creature may provide a summary on user-space OOM 
> killers. I have never tried them, but I expect that they may be more 
> intelligent than the kernel-space one. I have seen mentions of the 
> following ones: earlyoom, nohang, oomd.
>
> Do you have AI browser extensions that may load huge models in respect 
> to memory footprint?
>
>>> When the system starts to become sluggish, have you looked at the 
>>> firefox 'Task Manager' under tools to see if anything stands out?
>>
>> Previously I have seen the Isolated Web Co processes maxing CPU and 
>> the CPU fans starting to roar. Nothing unusual in content at the time 
>> and if I kill all ESR related processes it quiets down and I can 
>> resume the closed windows and tabs at much reduced CPU
>
> It is just a process that is responsible for some web pages. 
> JavaScript loaded for particular sites may leak. Videos may consume 
> RAM as well. I would not rely too much on ability of an application to 
> recover after killing of its specific processes. From my point of view 
> it is better to restart Firefox in such cases.
>
> Perhaps it is possible to find a particular site that causes issues, 
> but you need to inspect system namely when it is becoming sluggish.
>
> Firefox has the about:processes and about:performance tools. They may 
> be accessed from the about:about list.
>
> Try to sort top(1) output by memory ("M" key), try df(1) to check 
> tmpfs usage for the case that enough temporary video files are stored 
> there.
>
> I believed that 32G of RAM is still above that "average" users have, 
> so it should be enough. Other suggestions surprised me that 0.5G of 
> swap may significantly change anything since it is less than 2% of RAM.


I have discovered a magic bullet for solving running out of memory

sudo sync; sudo sh -c 'echo 3 > /proc/sys/vm/drop_caches'

Sadly it looks like I'll need to do this daily, simply for using Debian 
Bookworm with a variety of web browsers

Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

Isolated Web Co Session crash Firefox-ESR jeremy ardley <jeremy.ardley@gmail.com> - 2023-12-03 06:00 +0100
  Re: Isolated Web Co Session crash Firefox-ESR Tom Furie <tom@furie.org.uk> - 2023-12-03 06:40 +0100
  Re: Isolated Web Co Session crash Firefox-ESR Phil Wyett <philip.wyett@kathenas.org> - 2023-12-03 07:10 +0100
    Re: Isolated Web Co Session crash Firefox-ESR jeremy ardley <jeremy.ardley@gmail.com> - 2023-12-03 07:40 +0100
      Re: Isolated Web Co Session crash Firefox-ESR Phil Wyett <philip.wyett@kathenas.org> - 2023-12-03 07:50 +0100
        Re: Isolated Web Co Session crash Firefox-ESR jeremy ardley <jeremy.ardley@gmail.com> - 2023-12-03 08:10 +0100
          Re: Isolated Web Co Session crash Firefox-ESR Tom Furie <tom@furie.org.uk> - 2023-12-03 08:30 +0100
          Re: Isolated Web Co Session crash Firefox-ESR jeremy ardley <jeremy.ardley@gmail.com> - 2023-12-03 09:10 +0100
            Re: Isolated Web Co Session crash Firefox-ESR Phil Wyett <philip.wyett@kathenas.org> - 2023-12-03 10:40 +0100
            Re: Isolated Web Co Session crash Firefox-ESR Tom Dial <tddial@comcast.net> - 2023-12-04 02:50 +0100
      Re: Isolated Web Co Session crash Firefox-ESR Jeffrey Walton <noloader@gmail.com> - 2023-12-03 12:50 +0100
      Re: Isolated Web Co Session crash Firefox-ESR Michael Kjörling <2695bd53d63c@ewoof.net> - 2023-12-03 23:10 +0100
        Re: Isolated Web Co Session crash Firefox-ESR jeremy ardley <jeremy.ardley@gmail.com> - 2023-12-03 23:20 +0100
      Re: Isolated Web Co Session crash Firefox-ESR Max Nikulin <manikulin@gmail.com> - 2023-12-04 03:30 +0100
        Re: Isolated Web Co Session crash Firefox-ESR jeremy ardley <jeremy.ardley@gmail.com> - 2023-12-04 03:50 +0100
          Re: Isolated Web Co Session crash Firefox-ESR Max Nikulin <manikulin@gmail.com> - 2023-12-04 04:00 +0100
            Re: Isolated Web Co Session crash Firefox-ESR jeremy ardley <jeremy.ardley@gmail.com> - 2023-12-04 22:40 +0100
        Re: Isolated Web Co Session crash Firefox-ESR jeremy ardley <jeremy.ardley@gmail.com> - 2023-12-05 19:50 +0100
          Re: Isolated Web Co Session crash Firefox-ESR <tomas@tuxteam.de> - 2023-12-06 06:10 +0100
            Re: Isolated Web Co Session crash Firefox-ESR Karl Vogel <vogelke@pobox.com> - 2023-12-06 10:20 +0100
              Re: Isolated Web Co Session crash Firefox-ESR debian-user@howorth.org.uk - 2023-12-06 13:00 +0100
            Re: Isolated Web Co Session crash Firefox-ESR Max Nikulin <manikulin@gmail.com> - 2023-12-06 15:30 +0100
              Re: Isolated Web Co Session crash Firefox-ESR <tomas@tuxteam.de> - 2023-12-06 16:00 +0100
          Re: Isolated Web Co Session crash Firefox-ESR Max Nikulin <manikulin@gmail.com> - 2023-12-06 15:50 +0100
  Re: Isolated Web Co Session crash Firefox-ESR David Christensen <dpchrist@holgerdanske.com> - 2023-12-03 08:50 +0100
  Re: Isolated Web Co Session crash Firefox-ESR Reco <recoverym4n@enotuniq.net> - 2023-12-03 14:00 +0100

csiph-web