Re: [LUG] Chromium Browser

To: list@xxxxxxxxxxxxx

Subject: Re: [LUG] Chromium Browser

From: Simon Avery <digdilem@xxxxxxxxx>

Date: Tue, 18 Aug 2015 15:44:30 +0100

Delivered-to: dclug@xxxxxxxxxxxxxxxxxxxxx

Dkim-signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=dcglug.org.uk; s=1428397562; h=Sender:Content-Type:List-Subscribe:List-Help:List-Post:List-Unsubscribe:List-Id:Reply-To:Subject:To:From:Message-ID:Date:References:In-Reply-To:MIME-Version; bh=KBhnWEFZfeGuLenwnz8tQPGZqS/5ULuc5ZbXxcd6JJI=; b=URp4Md60U6EcTYAi5ywx/fbxv9XT/NiDDlUor55mwarMUkK1eyrmCCIYYFvogyUn52QtoYMGHbRpoCq6D5HAHYkQEIp+nJBeJvT3/+6RAR/Mglj0ZMPSc/7B0lZktscDm2kFnvF4KlVoPgv9WRyBZn0cTNBGTLk612/ErskdWB4=;

Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=LP4HqAQZXizRyUTQ8RSLx1eUVHPDdvD90XC7KAUKf2Y=; b=cI8z0ySP15bOj1gVfZUakmZsLDHa1c13S0brBimOfKtrOtjL2bmsXAQgpU8JaEVfeK zXbPzfS0uzxo5K0W2TqPH6Bv0B/82rXg7tfecIog9wyK5tp/ACUXYkdatoLkDXbt+7SB R0nThBjxYup0CfBEdH2c8KyFxafx2tSrgffQxkkcBlSaT2DdNTAZp/gfYmuad6pxp2Sk SfJey+BzA0NDkyeghotJlpVpBu2gKf1F9lKD71INdL62Hscy+zYBCQZb/+/wcIHO2uNh HF6ZHVfFHb7z7yh6NUNQH2lV3UFe614Dy0oOAO540gJjSW9UYqrlvgu38n5LpHvrXt1J IrTw==

For what it's worth, the only time I have process problems with Firefox
is when using it to view the Shop Security cams, after a few hours being
in a browser Tab, and then the Screensaver locks, try to get back in
again and All cores hit 100% for a bout 5 mims! before giving me the
desktop back. Killing Firefox helps but as tom says it would be nice to
just kill a tab.

mjpg memory issue. This was something that caused me some considerable problems too. Strangely enough, FF never used to have this issue - the bug was introduces sometime just before the version numbers went strospheric. I reported it and filed a bug report, but it was closed without resolution because it was deemed unlikely to cause problems to many people. It's disappointing that's still a problem after several years.

Simply put - I believe a jpg library used by FF was changed, and the new one did not release memory effectively. FF's memory usage continues to alloc as it receives images until there is no more. This was certainly the case on a windows client, I never used that aspect under linux. Â(Many cctv streams using mjpeg/mjpg which is just a collection of still images stitched together really fast, no audio).Â

If yours was mp4 or mpeg streams, then it may be something else.Â

My solution was to switch to chrome. Now - this also crashes on some streams after a long time (hours), but at doesn't take out other tabs, just displays the "Oh snap" page.