Unable to reproduce this issue on Ubuntu 14.04 using chrome latest stable M55-55.0.2883.75 by following steps mentioned in the original comment. Observed no crashes while scrolling the facebook page up and down.

abitthegray@ Are you able to reproduce this crash in incognito mode? If this is a consistent crash could you please provide sample crash ID's from chrome://crashes which will be really helpful for further investigation.

Thanks!

Just a copy-paste below from this debian bug tracking report if of any use.
Source: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846648
A ffmpeg flag seems to be involved.

I also observe the "aw, snap!" on gmail.com on my debian built 55.0.2883.75-1 amd64 chromium version.

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

Fixed by installing "libav-tools" (found on https://wiki.debian.org/ffmpeg).

As per comment #4 closing this issue, Please raise a new issue if you come across the similar one on latest chrome version.

Thanks!