the same issue with http://blogbankir.ru/

Unable to reproduce the issue on chrome latest stable M54-54.0.2840.87. Observed no crashes on navigating to skyeng.ru and http://blogbankir.ru/ . 

Reporter@ - Are you able to reproduce this issue on incognito mode as well? Could you please recheck this issue by upgrading your chrome to latest stable and by creating a new profile with no apps or extensions in your browser. If issue still persists please provide crash ID's from chrome://crashes.

Thanks!

>>Are you able to reproduce this issue on incognito mode as well?

yes, I could

>>Could you please recheck this issue by upgrading your chrome to latest stable

sorry, but I didn;t find any deb package for 54 version for my debian linux

>>and by creating a new profile with no apps or extensions in your browser.

with chrome://crash I have the following message

Crash reporting is disabled.
Crash reporting is not available in Chromium.


 If issue still persists please provide crash ID's from chrome://crashes

goga7777777@, could you please try it from "chrome://chrome" to update your existing browser and see if that works?

with chrome://chrome I don't see any possibility to update my chromium.

I have 32 bit version of chromium under debian linux distributive. I have to wait when debian developers will release 54 Chromium for 32 bit debian

Or is there other way to update my Chromium ? If yes, please share it 

Thank you for providing more feedback. Adding requester "brajkumar@chromium.org" for another review and adding "Needs-Review" label for tracking.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

have a look please on the same issue from others debian users
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823186

Unable to reproduce the issue on Ubuntu 14.04 using chrome stable #54.0.2840.100.

Attached a screen cast for reference.

Following are the steps followed to reproduce the issue.
------------
1. Navigated to URLs: toskyeng.ru and http://blogbankir.ru/
2. Observed that page loaded without any issues.

goga7777777@ - Could you please upgarde chrome to latest stable #54.0.2840.100 and please try to check this issue.
Also Precise-32 bit is no more supportive from M48 builds. Hence, please try with precise-64 bit.

Please try below link to download latest chrome stable for Linux.

https://www.chromium.org/getting-involved/dev-channel

Thanks...!!

Deleted: 662751.ogv 26.0 MB

662751.ogv 26.0 MB Download

my debian is 32 bit, that's why I can't test 64 bit version

right now I upgraded till 54.0.2840.101-1: i386 from here https://packages.debian.org/sid/chromium I still have the same issue as others debian users which reported about similar issue

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845785  

Thank you for providing more feedback. Adding requester "krajshree@chromium.org" for another review and adding "Needs-Review" label for tracking.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Just a copy-paste below from this debian bug tracking if of any use.
Source: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846648

Best,
Ara

From: Riku Voipio <riku.voipio@iki.fi>
To: Robert Lange <rlange@corusa.net>, 846648@bugs.debian.org
Subject: Re: [Pkg-chromium-maint] Bug#846648: another data point
Date: Fri, 9 Dec 2016 14:42:10 +0000
On Tue, Dec 06, 2016 at 04:02:00PM -0500, Robert Lange wrote:
> Debian stretch with chromium 55.0.2883.75-1 (and only chromium) pulled
> in from unstable. With a brand new profile (i.e., by deleting
> .cache/chromium and .config/chromium and starting Chromium) Chromium
> aw-snaps on gfycat.com with very high probability. I occasionally also
> see gmail aw-snap, but it's not consistent. When an aw-snap occurs, it
> does not seem to affect other tabs.

I managed to reproduce this. I tested a build with using embedded 
libraries of chromium, and the aw snap problem is gone. unbundling
libraries found the library that made the difference is ffmpeg.
Dropping the FF_API_CONVERGENCE_DURATION definition makes chromium
work fine with system ffmpeg again, gfycat.com, gmail and www.maap.it
no longer "aw, snap".

The gpu stacktraces people have passed in the bug might be another bug. 

--- a/media/ffmpeg/ffmpeg_common.h
+++ b/media/ffmpeg/ffmpeg_common.h
@@ -25,14 +25,14 @@
 // Disable deprecated features which result in spammy compile warnings.  This
 // list of defines must mirror those in the 'defines' section of FFmpeg's
 // BUILD.gn file or the headers below will generate different structures!
-#define FF_API_CONVERGENCE_DURATION 0
+// #define FF_API_CONVERGENCE_DURATION 0


 
> 
> Stack trace:
> 
> libpng warning: iCCP: known incorrect sRGB profile
> Received signal 11 SEGV_MAPERR fffffffd503afed7
> #0 0x55f8a1a8d77e <unknown>
> #1 0x55f8a1a8db39 <unknown>
> #2 0x7fca07207100 <unknown>
> #3 0x55f8a025af21 <unknown>
> #4 0x55f8a0260ffa <unknown>
> #5 0x55f8a02610bb <unknown>
> #6 0x55f8a5c0f612 <unknown>
> #7 0x55f8a12cf952 <unknown>
> #8 0x55f8a1ae7495 <unknown>
> #9 0x55f8a1b13c21 <unknown>
> #10 0x55f8a1aae629 <unknown>
> #11 0x55f8a1aafd9d <unknown>
> #12 0x55f8a1ab0240 <unknown>
> #13 0x55f8a1ab0e99 <unknown>
> #14 0x55f8a1ace66a <unknown>
> #15 0x55f8a1aeb296 <unknown>
> #16 0x55f8a1ae7322 <unknown>
> #17 0x7fca071fd464 start_thread
> #18 0x7fc9fc6229df clone
>   r8: 0000000000000000  r9: fffffffd503afecf r10: ffffe9c46ecdadef r11:
> 0011bb10e749bd95
>  r12: ffffffff00000000 r13: 00007fc9e5cb9548 r14: 00007fc9e5cb9540 r15:
> ffffe9c46ecdadef
>   di: 000016393e5b0f70  si: 0000000000000013  bp: 0000000000000006  bx:
> fffffffd503afecf
>   dx: fffffffd503afecf  ax: fffffffd503afecf  cx: 000016393ef75fa0  sp:
> 00007fc9e5cb94a0
>   ip: 000055f8a025af21 efl: 0000000000010286 cgf: 002b000000000033 erf:
> 0000000000000005
>  trp: 000000000000000e msk: 0000000000000000 cr2: fffffffd503afed7
> [end of stack trace]
> 
> _______________________________________________
> Pkg-chromium-maint mailing list
> Pkg-chromium-maint@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-chromium-maint

@reporter: Do you still see such crashes on the latest chrome version? I am unable to reproduce the issue on chromium version: 53.0.2785.143 Built on Ubuntu,running on Ubuntu 14.04(64 bit), Looks probably related to Debian.

Looping MTV team for help in triaging this further if Debian is available.

I migrated on Chromium Version 55.0.2883.75 built on Debian 9.0, running on Debian stretch/sid (64-bit) and don't have that issue. My the first report concerned 32bit version

Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot