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

Groups > linux.debian.user > #245244

Re: Memory leak

Show all headers | View raw

On Fri, 11 Feb 2022 18:06:52 +0000
piorunz <piorunz@gmx.com> wrote:

> On 11/02/2022 17:01, Celejar wrote:
> > So I've heard. So is this something I just have to live with? Does
> > everyone have this problem? I actually did used to kill firefox when I
> > was experiencing memory pressure - it certainly relieved the immediate
> > problem, but I think I found that not all the memory used was returned,
> > and when I restarted firefox, the problem of running out of memory
> > often returned before long (i.e., in much less time than after a fresh
> > install).
> 
> Yes that's typical for today's browsers. I never close browsers/reboot
> my home-work computer, right now I have 2 days uptime and 17 GB memory
> allocated between my normal day to day tools.
> 
> 
> Go to Firefox Settings / Performance
> Untick Recommended settings and change Content process limit to 1. Like
> in the screenshot.
> That will decrease memory usage.

Thanks - I'll look into this.

Celejar

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

Thread

Memory leak Celejar <celejar@gmail.com> - 2022-02-11 17:10 +0100
  Re: Memory leak Charles Curley <charlescurley@charlescurley.com> - 2022-02-11 18:00 +0100
    Re: Memory leak Celejar <celejar@gmail.com> - 2022-02-11 18:10 +0100
      Re: Memory leak Charles Curley <charlescurley@charlescurley.com> - 2022-02-11 19:50 +0100
        Re: Memory leak Celejar <celejar@gmail.com> - 2022-02-11 21:10 +0100
          Re: Memory leak Charles Curley <charlescurley@charlescurley.com> - 2022-02-11 23:40 +0100
        Re: Memory leak piorunz <piorunz@gmx.com> - 2022-02-11 21:20 +0100
      Re: Memory leak Celejar <celejar@gmail.com> - 2022-02-11 20:50 +0100
  Re: Memory leak Stefan Monnier <monnier@iro.umontreal.ca> - 2022-02-11 19:50 +0100
    Re: Memory leak Linux-Fan <Ma_Sys.ma@web.de> - 2022-02-11 20:20 +0100
      Re: Memory leak David Wright <deblis@lionunicorn.co.uk> - 2022-02-13 18:10 +0100
    Re: Memory leak Celejar <celejar@gmail.com> - 2022-02-11 20:50 +0100
      Re: Memory leak Stefan Monnier <monnier@iro.umontreal.ca> - 2022-02-12 18:50 +0100
        Re: Memory leak Celejar <celejar@gmail.com> - 2022-02-14 22:50 +0100
  Re: Memory leak "Roy J. Tellason, Sr." <roy@rtellason.com> - 2022-02-12 00:20 +0100
    Re: Memory leak piorunz <piorunz@gmx.com> - 2022-02-12 09:10 +0100
      Re: Memory leak Curt <curty@free.fr> - 2022-02-12 13:50 +0100
        Re: Memory leak piorunz <piorunz@gmx.com> - 2022-02-14 02:30 +0100
    Re: Memory leak Curt <curty@free.fr> - 2022-02-12 11:20 +0100
      Re: Memory leak rhkramer@gmail.com - 2022-02-12 15:30 +0100
        Re: Memory leak Felmon Davis <moelmoel2714@gmail.com> - 2022-02-12 23:50 +0100
        Re: Memory leak <tomas@tuxteam.de> - 2022-02-13 07:30 +0100
          Re: Memory leak rhkramer@gmail.com - 2022-02-13 16:10 +0100
            Re: Memory leak <tomas@tuxteam.de> - 2022-02-13 16:20 +0100
            Re: Memory leak "Andrew M.A. Cater" <amacater@einval.com> - 2022-02-13 17:10 +0100
        Re: Memory leak "Roy J. Tellason, Sr." <roy@rtellason.com> - 2022-02-13 21:00 +0100
          Re: Memory leak rhkramer@gmail.com - 2022-02-14 02:20 +0100
      Re: Memory leak Felmon Davis <moelmoel2714@gmail.com> - 2022-02-12 23:50 +0100
        Re: Memory leak <tomas@tuxteam.de> - 2022-02-13 07:40 +0100
          Re: Memory leak Tixy <tixy@yxit.co.uk> - 2022-02-13 09:10 +0100
            Re: Memory leak Andrei POPESCU <andreimpopescu@gmail.com> - 2022-02-13 17:10 +0100

csiph-web