I tried to find Skbitmap.h in the chromium source code but gave up after some minutes. I assume https://github.com/google/skia/blob/c7ec7c9cabf5c8ad08beb617b99831ece25dacdd/include/core/SkBitmap.h is used though. So, the error is apparently thrown when calling the the tryAllocPixels method. This indicates that my outdated graphics driver (xf86-video-ati 1:7.2.0-1) might share some blame ;-)
Anyway, I get the feeling that this bug will be next to impossible to reproduce for you. 

Unable to reproduce the issue on  Linux Ubuntu-14.04 using chrome stable version 54.0.2840.100 and chromium market stable version with below steps
1.Opened chromium
2 Played diep.io for 35 minutes.
Not observed any crash.
could you please let us know if anything missed here to reproduce the issue.

Thanks..

I have been trying to reproduce this bug with my laptop (nearly the same software except drivers ofc) and it didn't crash so far.

Starting chromium with --enable-logging --v=1 produced this now:

chromium --enable-logging --v=1
[5880:5880:1125/192249:ERROR:browser_main_loop.cc(260)] Gtk: Im Modulpfad »adwaita« konnte keine Themen-Engine gefunden werden,
[5880:5880:1125/192249:ERROR:browser_main_loop.cc(260)] Gtk: Im Modulpfad »adwaita« konnte keine Themen-Engine gefunden werden,
[5880:5880:1125/192249:ERROR:content_settings_pref.cc(469)] Invalid pattern strings: {*.]christianforst.de,*
[5880:5880:1125/192249:ERROR:content_settings_pref.cc(295)] Invalid pattern strings: {*.]christianforst.de,*
[6055:6055:1125/192251:ERROR:sandbox_linux.cc(343)] InitializeSandbox() called with multiple threads in process gpu-process. 
[5880:5880:1125/192259:ERROR:CONSOLE(73)] "Uncaught TypeError: Cannot read property 'addExtensions' of undefined", source:  (73)
Received signal 11 SEGV_MAPERR 000000000020
#0 0x55896cf0789e <unknown>
#1 0x55896cf07c59 <unknown>
#2 0x7ffb15c95080 <unknown>
#3 0x55896d4c4e80 <unknown>
#4 0x558970dfa674 <unknown>
#5 0x558970dfa868 <unknown>
#6 0x558970dede06 <unknown>
#7 0x55896f1ab064 <unknown>
#8 0x55896ffa92d6 <unknown>
#9 0x55896ffaae39 <unknown>
#10 0x55896fde1dea <unknown>
#11 0x55896bd46bd9 <unknown>
#12 0x55896bdd34e5 <unknown>
#13 0x55896bdd419c <unknown>
#14 0x3cfc4bc063a7 <unknown>
  r8: 000055897f2b4100  r9: 0000000000000000 r10: 0000000000000000 r11: 000000000000000b
 r12: 000055896d5c3d50 r13: 0000000000000007 r14: 0000000000000002 r15: 00007ffe16665df0
  di: 0000000000000000  si: 000055897f75ff78  bp: 00007ffafc006da0  bx: 000034e8917a0b90
  dx: 4489e00044f2e000  ax: 00005589735706a8  cx: 0000000000000000  sp: 00007ffe16665b78
  ip: 000055896d4c4e80 efl: 0000000000010206 cgf: 002b000000000033 erf: 0000000000000004
 trp: 000000000000000e msk: 0000000000000000 cr2: 0000000000000020
[end of stack trace]

I guess this makes my assumption (comment 3) more likely that it is a combination of hardware (and video driver) & software that causes the crash more likely. 
As a consequence, I don't think I can provide any instructions how to reproduce this for you reliable (apart from shipping my computer to you :))

Tagging Skia in case they have anything to look at, but, in general, if it's a crash in some Linux distribution's Chromium-derivative package, you should report bugs there. They'll, one hopes, be able to symbolize your crash and whatnot.

Yeah I don't think there's anything we can do here in Skia, with it being so hard to repro/get a full stack and seemingly tied to specific hardware/older drivers.  If you continue to dig into it and get more info, feel free to reopen and provide that.