Full Version: Chromium Instability
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Noticed a the thread on Firefox.... Since its a different application I created one for chromium. 

Using the 2G pine64.

After installing chromium. Chromium will launch but will give the "Aw, Snap" for most any action (browse to external page or internal page like settings). 

I can create tabs however, those tabs just load the "Aw, Snap" page.

Any thoughts....
I can say that I've also encountered the chromium thing (I'm the one who started the firefox thread).  Leoncito81 suggested checking my pacman sources/install settings (I haven't had a chance to look into this, which may take me a bit since I'm new to the arch/pacman setup), but it is sounding like that might be our problem (hopefully).

Start chromium from terminal with:
chromium --disable-seccomp-filter-sandbox

Works for me.
(04-24-2016, 04:26 AM)geffas Wrote: [ -> ]
(04-23-2016, 02:32 PM)baryluk Wrote: [ -> ]It works!

[Image: mpnBz7w.png]

(High CPU usage is mostly due to the fact that MATE system monitor is consuming quiet a bit of cpu for drawing stuff. When using top, chromium is using few % when idle basically)

Remember to run with:

$ chromium --disable-seccomp-filter-sandbox

(probably due to the bug in the old kernel, seccomp and seccomp filter is in 3.10.65 according to /proc/config.gz)


Debian bug:

There should also be 49.0 in debian experimental, didn't checked it yet.

I can confirm this also works for chromium under Arch Linux. chromium --disable-seccomp-filter-sandbox fixes the awww snap error that occurs after starting chromium under arch.

Try this and see if it works. :-)