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

Groups > linux.debian.user > #159556

Re: Tracking down memory leaks

Show all headers | View raw

On 10/18/2015 12:53 PM, Don Armstrong wrote:
> On Sat, 17 Oct 2015, Marc Shapiro wrote:
>> When I do have to do a reboot I close down everything to a single
>> console running. I then run top and it only shows bash and top. Next
>> time I will run top and include root and daemon processes and see if
>> anything shows up. I am guessing that this is memory that Firefox was
>> using, but has forgotten about. If that is the case, is there a way to
>> free it up without doing a reboot?
> [...]
>>   5062 marc      20   0 7622m 5.3g  12m D   1.6 68.1 210:02.01 firefox
>
> First off, firefox isn't something that Debian distributes. So odds are
> that whatever version you're using is old and outdated, or you're using
> a plugin or add-on which is buggy.
No, it's current.  I get it directly from the Mozilla site whenever 
there is a new release.  I am currently running 40.0.2.
> Secondly, in firefox or iceweasel, about:memory will show you want it is
> doing and where it is spending its memory.
>
> Finally, if you kill off the firefox process, it will stop using the
> memory, and the memory will become free again without you doing
> anything else.
>
>
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

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