Clever Geek Handbook

Is there a way to find the root cause of Google Chrome "Aw, Snap"?

We have a Javascript library that provides the core of our main product. Over the past couple of days, Google Chrome has been throwing a "Aw, Snap! Something went wrong" blue screen when I try to run this library.

The library works great in other browsers and also works great with all my copies of Chrome.

What I'm looking for is some kind of log on Google Chrome that could point me in the right direction. Is there such a thing?

+3
javascript google-chrome


source to share


No one has answered this question yet

See similar questions:

61
How do I get more information when the "Aw Snap" screen appears in Chrome?
22
Is there a limit on the number of users in the Google Chrome browser?
20
Maximum memory usage by chrome process (tab) and how to increase it?

or similar:

692
Best way to find an element in a JavaScript array?
312
Is there a way to get xpath in google chrome?
118
Javascript switcher vs. if ... else if ... else
21
How do I stop Chrome from redirecting to HTTPS?
3
Insecure JavaScript attempt to access frame in Google Chrome
3
Chrome Web Audio Feedback API latency
1
Debug Chrome on Google TV
0
Any way to package Sencha Touch app as installed in Google Chrome?
0
Why is Chrome 65 6x slower than other browsers?
0
Scoll to bottom div detection for different users of the same pc


More articles:


All Articles
Loading...
X
Show
Funny
Dev
Pics