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


Groups > linux.debian.user > #264145

Re: Isolated Web Co Session crash Firefox-ESR

From Phil Wyett <philip.wyett@kathenas.org>
Newsgroups linux.debian.user
Subject Re: Isolated Web Co Session crash Firefox-ESR
Date 2023-12-03 10:40 +0100
Message-ID <HGR7b-aL96-3@gated-at.bofh.it> (permalink)
References (2 earlier) <HGOiZ-aJtY-1@gated-at.bofh.it> <HGOsG-aJxe-1@gated-at.bofh.it> <HGOM1-aJSw-3@gated-at.bofh.it> <HGPf3-aK1z-5@gated-at.bofh.it> <HGPI5-aKry-5@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


[Multipart message — attachments visible in raw view] - view raw

On Sun, 2023-12-03 at 16:00 +0800, jeremy ardley wrote:
> 
> On 3/12/23 15:37, Phil Wyett wrote:
> > Not to regurgitating info here, I will add a link below that will 
> > instruct how to adjust or disable oom-killer in a sensible manner if 
> > you wish to experiment (your choice and being cautious :-)) if it is 
> > in fact the oom-killer algorithm that is the main cause of your issue.
> 
> 
> The issue is not so much Isolated Web Co being terminated, but my entire 
> Mate session being terminated.
> 
> I wouldn't have too much problem if OOM-killer hit Firefox. I have done 
> it myself when things got slow.
> 
> However, I can't see any valid reason for the Mate session to be 
> assassinated? Or at least be inevitable collateral damage.
> 

Hi,

Not being deeply familiar with the oom-killer heuristics, I could not offer reasoning why 'mate' is
killed. These heuristics by default kill the most memory hogging processes in theory and the
consequences of this on other processes I cannot comment on.

There is one setting you may wish look at and consider.

Reading:

https://docs.kernel.org/admin-guide/sysctl/vm.html

I see the following:

https://docs.kernel.org/admin-guide/sysctl/vm.html?highlight=laptop#oom-kill-allocating-task

Setting this to '1' may trigger a strategy that does not put 'mate' in the firing line as it changes
the target for killing to the process call that triggers the out of memory condition. I am sure if
my reading of this setting is wrong, someone will correct.

This would be done of course at your own risk after doing the research yourself.

Regards

Phil

-- 
Playing the game for the games sake.

Web:

* Debian Wiki: https://wiki.debian.org/PhilWyett
* Website: https://kathenas.org

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