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

Groups > linux.debian.user > #159644

Re: Tracking down memory leaks

Show all headers | View raw

Quoting Marc Shapiro (marcnshap@gmail.com):
> On 10/20/2015 11:33 PM, Jörg-Volker Peetz wrote:
> >Marc Shapiro wrote on 10/21/2015 06:52:
> ><snip>
> >>Something is not freeing up memory.  It may, or may not be Firefox, but...  I
> >>can exit all programs and all instances of X, leaving only a single console
> >>running.  Top will show itself and bash, nothing else, but free can show over
> >>2GB used.  If I then reboot, free will show only about 250 MB used.  Obviously
> >>something was tying up nearly 2 GB and it took a reboot to free it up.
> >>
> >>Marc
> >>
> >Which version of free you are using?
> >Where does it show 2 GB?
> >Do the 2 GB comprise buffered and cached data?
> >Please, show the the output of free.
> Don Armstrong had also suggested checking the cache and buffers,
> which I had forgotten to do when I restarted.  I checked them
> yesterday and, yes, that is where most of the memory was going after
> I had exited all X sessions.  Google was my friend and showed me how
> to free up that memory ('free && sync && echo 3 >
> /proc/sys/vm/drop_caches && free' as root) and all is now good with
> the world.
> 
> Thanks, everyone, for the help.  If I had just looked more closely
> at the output of 'free' I could have done this myself.   (Forehead
> slap).

I notice you've flagged this posting with SOLVED. However, I can't
find where you reported a problem. The original posting only says:

"I could run for months without having a memory problem. Now it's every
few days. When this happens,..."

So what was the problem? What happens?

Cheers,
David.

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

Thread

Tracking down memory leaks Marc Shapiro <marcnshap@gmail.com> - 2015-10-13 16:30 +0200
  Re: Tracking down memory leaks The Wanderer <wanderer@fastmail.fm> - 2015-10-13 16:40 +0200
  Re: Tracking down memory leaks Don Armstrong <don@debian.org> - 2015-10-13 17:00 +0200
    Re: Tracking down memory leaks Marc Shapiro <marcnshap@gmail.com> - 2015-10-17 18:10 +0200
      Re: Tracking down memory leaks Don Armstrong <don@debian.org> - 2015-10-18 22:00 +0200
        Re: Tracking down memory leaks Marc Shapiro <marcnshap@gmail.com> - 2015-10-21 07:00 +0200
          Re: Tracking down memory leaks Jörg-Volker Peetz <jvpeetz@web.de> - 2015-10-21 08:40 +0200
            Re: Tracking down memory leaks (SOLVED) Marc Shapiro <marcnshap@gmail.com> - 2015-10-22 16:30 +0200
              Re: Tracking down memory leaks (SOLVED) Nicolas George <george@nsup.org> - 2015-10-22 16:40 +0200
                Re: Tracking down memory leaks (SOLVED) Cindy-Sue Causey <butterflybytes@gmail.com> - 2015-10-23 19:30 +0200
                Re: Tracking down memory leaks (SOLVED) Nicolas George <george@nsup.org> - 2015-10-23 19:40 +0200
                Re: Tracking down memory leaks (SOLVED) Lisi Reisz <lisi.reisz@gmail.com> - 2015-10-23 20:10 +0200
                Re: Tracking down memory leaks (SOLVED) The Wanderer <wanderer@fastmail.fm> - 2015-10-23 20:40 +0200
                Re: Tracking down memory leaks (SOLVED) Reco <recoverym4n@gmail.com> - 2015-10-23 20:20 +0200
                Browser tabs, was Re: Tracking down memory leaks David Wright <deblis@lionunicorn.co.uk> - 2015-10-23 21:00 +0200
              Re: Tracking down memory leaks David Wright <deblis@lionunicorn.co.uk> - 2015-10-22 17:30 +0200
                Re: Tracking down memory leaks Marc Shapiro <marcnshap@gmail.com> - 2015-10-24 08:30 +0200
              Re: Tracking down memory leaks (SOLVED) <tomas@tuxteam.de> - 2015-10-23 09:40 +0200
        Re: Tracking down memory leaks Michael Jones <mj@mikejonesey.co.uk> - 2015-10-21 23:40 +0200
  Re: Tracking down memory leaks Michael Jones <mj@mikejonesey.co.uk> - 2015-10-21 23:30 +0200
  Re: Tracking down memory leaks Michael Jones <mj@mikejonesey.co.uk> - 2015-10-21 23:40 +0200

csiph-web