Re: Memory leak

From	Celejar <celejar@gmail.com>
Newsgroups	linux.debian.user
Subject	Re: Memory leak
Date	2022-02-14 22:50 +0100
Message-ID	<DQRol-1PNo-5@gated-at.bofh.it> (permalink)
References	<DPGEF-16Zt-5@gated-at.bofh.it> <DPJ9v-18kD-5@gated-at.bofh.it> <DPK5z-18TG-1@gated-at.bofh.it> <DQ4GZ-1lwh-1@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

On Sat, 12 Feb 2022 12:49:15 -0500
Stefan Monnier <monnier@iro.umontreal.ca> wrote:

> > As I mentioned (briefly) in my original post, yes, I experience concrete
> > problems: the system either grinds to a halt or becomes unresponsive,
> > or hits swap and becomes intolerably slow.
> 
> Sorry I missed that part.
> I think that's what you should focus on: try and run some background
> collection of timestamped system state (CPU use and memory use) and then
> try and investigate to see what it is that was eating all the resources
> during those times where the system grinds to a halt.

Thank you. I actually just did a complete rebuild of my system from
scratch: the old SSD was almost full and I installed a new one, so I
decided to rebuild from scratch to get rid of accumulated cruft. So far
things have been much better, but I'll see if problems return.

Celejar

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