Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Does anybody know if there is a practical way to determine the cause of the "Aw Snap" message that occasionally appears on Google Chrome? Does Chrome have an error log I can refer to? I'm suspecting this issue is caused by a recursive loop in the code which is then swallowing up all the memory? Is there any way I can confirm this?

share|improve this question
up vote 7 down vote accepted

THere is, see explanations here: for ordinary logging in Chrome, you could try this and this for javascript.

share|improve this answer
    
I think the first option will help isolate this problem. The dev console hangs before it can output anything of use. – QFDev Jun 14 '13 at 9:02
    
I enabled the log and upon chrome crash, it didn't logged any error at the time of crash. Is there any reference that could provide insights into the log items? – Khadim Ali Jan 25 at 13:49
    
Is this chromium page about logging.h what you want? – vinnief Jan 26 at 20:32

The offical Chrome Developers Twitter account linked to a website which helps you to debug the "Aw snap" pages: http://www.chromium.org/for-testers/enable-logging

The recommendation is to launch Chrome with these flags:

--enable-logging --v=1

If you do that, then you can grab a crash log from the file chrome_debug.log in Chrome's user data directory (in the parent directory of Default/) or in the binary build folder (out\Debug) if you are using a debug build.

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.