My thoughts confirmed.... about 13.10

[Peter Smout]

On 11/04/14 05:27, J wrote:
> On Fri, Apr 11, 2014 at 12:02 AM, c. marlow <chris at marlows.org> wrote:
>> On Thu, 2014-04-10 at 22:36 -0400, Rashkae wrote:
>>> On 14-04-10 09:30 PM, c. marlow wrote:
>>>> On Thu, 2014-04-10 at 20:55 +0100, Colin Law wrote:
>>>>> On 10 April 2014 18:12, c. marlow <chris at marlows.org> wrote:
>>>>>> On Thu, 2014-04-10 at 17:29 +0100, Colin Law wrote:
>>>>>>> On 10 April 2014 16:57, c. marlow <chris at marlows.org> wrote:
>>>>>>>> I just googled my issue and it DOES look like 13.10 does have a memory
>>>>>>>> leak issue and the only thing you can do when it gets up real high is
>>>>>>>> either log off and back on to get it down from 1.1 gig back to 400 mb or
>>>>>>>> go and kill gnome-session and when it takes you back to the log in
>>>>>>>> screen just sign back in.... or when I get done just log off everytime
>>>>>>>> and sign in when im ready to get back on the computer
>>>>>>>>
>>>>>>>> ugh......... just my luck I should of installed 13.04 or 12.04
>>>>>>> I have not seen any such issues.  Is there a bug report for this?
>>>>>>> Does the system monitor show that a particular app is using lots of memory?
>>>>>>>
>>>>>>> You could always try 14.04.  Not much point installing 13.10 at the
>>>>>>> moment anyway when the next version is due any day.
>>>>>>>
>>>>>>> Colin
>>>>>>>
>>>>>>
>>>>>> This was taken this morning Colin, I left NOTHING open... I went to bed
>>>>>> forgot to put pc in standby and just had turned the monitor off. I woke
>>>>>> up around 2 am and saw this.
>>>>>>
>>>>>> http://i886.photobucket.com/albums/ac69/CMAR606/UBUNTU/damnunity_zps86c07b3b.png
>>>>> It is using less than half of the available RAM and virtually no swap.
>>>>>    That is probably nothing to worry about.  Linux will use available
>>>>> RAM for disk buffers and so on when it can in order to speed up the
>>>>> system.  If that is what is happening then the memory will be freed up
>>>>> if it is required.
>>>>>
>>>>> If there were a significant memory leak then you would probably the
>>>>> swap usage go up.
>>>>>
>>>>> Next time it happens run top in a terminal and post the two lines
>>>>> showing the memory usage.
>>>>>
>>>>> Colin
>>>>>
>>>>
>>>> Ok Here you go here is my TOP ....  I walked away came back and Ubuntu
>>>> was at 1.1 gig being used.
>>>>
>>>> http://i886.photobucket.com/albums/ac69/CMAR606/UBUNTU/TOP.jpeg
>>>
>>> Well, that shows your culplit pretty clear, Firefox and
>>> "plugin-container" with 70% cpu usage, as well as 700+MB of memory for
>>> that alone... you left a browser window open on a site with a demanding
>>> flash thingy?
>>>
>>
>>
>> Nope because I got up at 2 am this morning and got on the pc and it was
>> using 1.3 gigs and nothing was left open.
>>
>
> Dump firefox and get Chrome...
>

Hi,

This hardly seems an answer, Ubuntu ships with Firefox as it's default 
browser, and any newbie has the right to expect it to 'just work'(tm) 
and a blanket "dump firefox for chrome(ium)" is hardly helpful!


> This is a problem with Firefox, or if not specifically firefox, with
> the plugins you have installed.  That's why you see plugin-container.
> Watch it long enough, and you should see it slowly climb higher...
>
> Another thing you need to do, is run top, but sort on the Res column.
> Virt is the total memory size including what the app has mapped for
> itself, any cached pages, etc., but Res is what's actually in RAM at
> the moment.
>
> http://mugurel.sumanariu.ro/linux/the-difference-among-virt-res-and-shr-in-top-output/
>
> Anyway, I used to see this maddeningly as it would cause me to have to
> reboot every two days because the browser plugins would constantly
> chew up memory and never release it.  Eventually I dumped Firefox
> completely and just use Chrome on my linux boxes today.  Chrome has
> its own issues but it seems to work far better than Firefox.
>
> Cheers
> Jeff
>
I have noticed the 'plug-in container' using a fair bit of my memory, 
but it releases it when closed (the offending plug-in for me is 
flash-player (non free)) <note:> I have tried gnash but it is NOT 
compatible with all websites most notably youtube.com

I do not leave f-fox running all day open on any of my machines but as 
an experiment I will leave it running tonight (not playing just open) 
and see if I can replicate this and try to start debugging ;)

Let's see if we can solve this (or at least try and find if it is a 
*buntu related or perhaps it's Adobe's fault (their Linux support has 
been awful for a couple of years now :(  .) and deed it back up stream 
to the relevant party (Mozilla, Adobe or the *buntu devs)

Regards

Pete S