Take the 2-minute tour ×
Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

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

1 Answer 1

up vote 3 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. –  QF_Developer Jun 14 '13 at 9:02

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.