| 1 |
On Sat, 24 Jan 2015 16:43:41 +0100 Nils Holland wrote: |
| 2 |
> Hi folks, |
| 3 |
> |
| 4 |
> I've been using chromium successfully on my ~x86 system for quite a |
| 5 |
> long time, but starting with the last two updates that came in during |
| 6 |
> the last few days (namely, chromium-40.0.2214.85 and |
| 7 |
> chromium-40.0.2214.91), I started having problems. |
| 8 |
> |
| 9 |
> Both of these versions build just fine, but upon trying to launch |
| 10 |
> them, the browser's interface comes up just fine, but will only |
| 11 |
> display a "Something went wrong..." page. I can try typing in and |
| 12 |
> accessing URLs, but all I will ever get is this error page. |
| 13 |
> |
| 14 |
> That's not all, though, I also get to see error messages, namely the |
| 15 |
> following in my terminal: |
| 16 |
> |
| 17 |
> ../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf |
| 18 |
> failure in syscall 0265 |
| 19 |
> |
| 20 |
> And this here in dmesg: |
| 21 |
> |
| 22 |
> chrome[5274]: segfault at e806109 ip b5c5c945 sp ac280980 error 6 in |
| 23 |
> chrome[b1864000+5eed000] |
| 24 |
> |
| 25 |
> Great, I thought, something wrong with the sandbox stuff. So I tried |
| 26 |
> to launch chromium without it ("chromium --no-sandbox"), and indeed: |
| 27 |
> The browser works absolutely fine this way - I get none of the |
| 28 |
> problems or messages mentioned above. |
| 29 |
> |
| 30 |
> Of course, I tried to find a related entry in both the Gentoo as well |
| 31 |
> as the chromium bug trackers, but I couldn't find anything in either. |
| 32 |
> I'm a bit reluctand to report my own bug as I wouldn't be 100% sure |
| 33 |
> that I'm not causing the problem (after all, I'm building my chromium |
| 34 |
> with USE=custom-cflags, which is not officially supported, but has |
| 35 |
> always produced nicely working builds for me in the past), so I |
| 36 |
> thought I'd ask here first if I'm the only one observing this |
| 37 |
> behavior. |
| 38 |
> |
| 39 |
> The question, thus, would probably be: Anyone using one of the recent |
| 40 |
> chromium-40 versions on ~x86 or anywhere else and seeing something |
| 41 |
> similar? Or probably someone who has experienced something like that |
| 42 |
> before and could offer a guess what might be wrong here - a real bug, |
| 43 |
> custom-cflags, or something entirely different? |
| 44 |
|
| 45 |
I gave up on chromium starting from chromium-36, where they dropped |
| 46 |
pre-SSE2 x86 support (and I use such system: Athlon-XP). I tried to |
| 47 |
re-add this stuff with partial success (works, but still SIGILLs |
| 48 |
sometimes) and it's very hard to clean all pieces. Looks like |
| 49 |
they're slowly abandoning x86 and older hardware at all. |
| 50 |
|
| 51 |
Best regards, |
| 52 |
Andrew Savchenko |
Archives