While I have no experience with the Chrome browser, doing some searches has
revealed the matter to be one involving errors in the developer codes from Google.
And there is some suspicion the Flash plugin or player could contribute to the error.
Some users have reverted to an older (beta?) of Chrome, where this issue was not
as evident; but I am not sure if that was before a later version of Flash player. Or, if
the idea of this reversion pre-dated other later software updates that pushed the
issue into being (again) in the Chrome browser. Perhaps some coding also used in
another version of Chrome has been added to the Mac version now.
From the google search I just launched, using these words...
*Mac OS X: what causes google aw snap error and how do i fix it?*
... I see there has been some issues for some time now. Whether
or not they all stem from a similar coding error which morphed yet
again, further into the final error that appears common, after a new
catalyst, is a question that bears consideration.
One item I noticed, among others, was this statement:
"...+'Aw Snap' is basically the generic error we show when Google+
+Chrome crashes, but there are many different causes for a crash+..."
The google user forums probably point to the majority of users whose
operating system is representative of a larger population; so most of
them would show Windows users as one prime group. There have
been ubuntu unix and other users who have noted the error when
attempting to open web pages in their Chrome browser.
Hopefully by posting this here, you will be able to get more involved
persons into the conversation; or at least more possible page links
and places to look for some ideas on what other Mac users, who've
seen little or no support elsewhere, have tried to do to correct this.
While I only have and use four browsers, there is a feeling of relief
to me, that one of them is not Chrome (not supported in my Macs.)
Good luck in this matter! 🙂
