UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.100 Safari/537.36

Steps to reproduce the problem:
1. Open Chrome without the --disable-gpu flag
2. Watch it all burn

What is the expected behavior?
Using the browser

What went wrong?
I'm running Ubuntu 16.10 with Cinnamon in a VirtualBox (I'm concerned this might be a big part of the problem) with 2 screens, 128MB of video memory, and 3d acceleration enabled. It's been working find (with only 96MB of memory) until I installed Chrome and tried to open it. The attached screen snip is from one of the times I was able to get chrome to actually close. It doesn't display anything when it opens, just blank with artifacts. Since then, I can't even get chrome to close and had to simply power off the VM (wasn't responding to the shutdown signal). Per this issue (https://productforums.google.com/forum/#!topic/chrome/K8dQhySDL9I) I added the --disable-gpu flag and I'm filing this report from chrome in the VM. It's worth noting that there's nothing on chrome://crashes. 

Crashed report ID: No

How much crashed? Whole browser

Is it a problem with a plugin? No 

Did this work before? No 

Chrome version: 54.0.2840.100  Channel: stable
OS Version: Ubuntu 16.10 with Cinnamon
Flash Version: Shockwave Flash 23.0 r0

I hope this is correctly filed as a crash, it's hard to tell since it's not truly crashing, just getting stuck.
 

Deleted: Capture.PNG 79.8 KB

	Capture.PNG 79.8 KB View Download