I have the same issue with "Aw, snap" on all sites which were mentioned
on this tread.
Here is topic which I have created
https://bugs.chromium.org/p/chromium/issues/detail?id=662751&can=2&start=0&num=100&q=snap&colspec=ID%20Pri%20M%20Stars%20ReleaseBlock%20Component%20Status%20Owner%20Summary%20O
I can add that this bug affects 52.0.2743.116-2 in stretch on i386.
Searching Google for (for example) "define:donkey" seems to reproduce the
bug reliably.
I am currently using 49.0.2623.108-1, which was the most recent unaffected
version I could find.
Martin Lester.
unsubscribe
On Mon, Aug 15, 2016 at 4:52 PM, Mert Dirik wrote:
> On Fri, 10 Jun 2016 02:02:59 -0400 Michael Gilbert
> wrote:
> > > How about stack traces from a first message? Are they useless?
> >
> > Without debugging symbols, basically yes.
> >
> > > If you want full backtrace from gdb then
I am having the same problem. When I visit
http://www.classicalkusc.org/stream/listen.html and click the Play button
(triangle in the middle) to stream music, chromium crashes with aw, snap.
Version: 51.0.2704.79-1, crashes
Version: chromium_51.0.2704.63-1-deb8u1_i386.deb, works great.
I disable
> How about stack traces from a first message? Are they useless?
Without debugging symbols, basically yes.
> If you want full backtrace from gdb then describe how to get if, because
> usual approach (gdb --> run --> segfault --> bt full) will not
> work with chromium as far as I understand.
htt
Hi,
> A backtrace that includes chromium's debugging symbols would be more
> helpful than the "me too" messages.
How about stack traces from a first message? Are they useless?
If you want full backtrace from gdb then describe how to get if, because usual
approach (gdb --> run --> segfault --> b
control: tag -1 help, moreinfo
control: retitle -1 chromium: i386 build crashes on many websites
A backtrace that includes chromium's debugging symbols would be more
helpful than the "me too" messages.
The biggest difference from deb8u1 is embedded instead of system
ffmpeg. It would be useful to
Package: chromium
Followup-For: Bug #823186
I can verify that it is fixed in 51.0.2704.63-1~deb8u1, but still broken in
51.0.2704.63-2 on an i386 system.
My test website is https://calendar.google.com/ (I saw similar results on
https://mail.google.com/mail/u/0/, but didn't test as care
Package: chromium
Version: 51.0.2704.63-2
Followup-For: Bug #823186
Dear Maintainer,
Please note that this issue is still present in 51.0.2704.63-2
Regards,
Toote
-- System Information:
Debian Release: stretch/sid
APT prefers testing
APT policy: (990, 'testing')
Architec
On my girlfriend's laptop, chromium 50.0.2661.94-1 was crashing on all websites
that were attempted with "aw snap" and the same message:
ERROR:zygote_host_impl_linux.cc(162)] Failed to adjust OOM score of renderer
with pid ... : Permission denied
It's running stretch amd64, fully up to date, us
I confirm Chromium works well using the Stretch version
50.0.2661.94 on a new 64 bit system on the samemachine as
the buggy same version using a 32 bit system ondifferent
partition.
Buthow did security get the same version working on 32 bit?
Hi,
I have tested Chromium 50.0.2661.94-1 on few other PCs and laptop and there are
such results:
* it works absolutely fine on PC and laptop with amd64 Debian Sid systems
* it crashes at tested web sites on PC with i686 Debian Sid system
(as well as on my laptop with i686 Debian Sid system)
It
Interestingly neither the new package chromium (50.0.2661.94-1~deb8u1)
[security] nor theprior stable versionhave the Aw
snap! in gmailbug,
unlike the Sid 50.0.2661.94 version.
Same as 821463.
control: reopen 823186 =
control: notfixed 823186 50.0.2661.75-2
control: severity 823186 important
Hi,
>> Chromium become completely unusable at many websites since version
>> 50.0.2661.75-1. See screenshot and stack trace examples in attachments.
>> And this is not duplicate of bug #821154,
14 matches
Mail list logo
