Snap problem

[Wooden shoe]

I have had this happen a number of times.
When inserting a emoticon and then hit the enter key, SNAP happens and my message disappears.
I am a one finger keyboarder so this is frustrating.
I suspect a glitch somewhere in this program as it only happens on this website.

[Eckhart Aurelius Hughes]

Thank you for reporting this issue. Thank you for reporting this problem. Unfortunately, I have researched 'aw, snap' errors occurring on a certain page for a certain user before and just like this time have come up with no solution. I find other official tickets reporting the same general problem (a single webpage delivering reproducible 'aw snap' errors to users) submitted to Google's Chrome support but with no solutions or explanations offered by Google. This appears to be a known bug in Chrome. If you are interested, you can check out these similar issues with no explanation or solution:

Issue 95484
unresolved 5/21/10
unresolved issue from 1/13/11

If any of those or others like them had been solved with details provided, it would provide a much better starting point for how to deal with this. But I have researched a lot and not found a single time an explanation or solution has been provided to someone reporting such an issue. Chrome support does provide many suggestions, advice, and explanations for users who experience 'aw, snap' on every website, but none as far as I can tell for the numerous people reporting the issue just on one or a few certain website/pages--even though issues have been reported.)

Personally, I find that Firefox crashes much less often and more importantly even after Firefox crashes I am able to restore my session with all my form data still in tact (e.g. on this site if Firefox or my whole computer crashes or accidentally is shut off while I am writing a post, I can easily recover the page with the post still in the box). So that's why I personally have switched back to Firefox.

Anyway, I will continue to find a way to deal with this Chrome-compatibility issue--not just for your particular case but for any other times past and future that someone reports a certain page generating reproducible 'aw snap' messages in Chrome. But you may have more luck officially reporting the bug to Google. If you do report it to Google, please send me the link or issue number so I can track it.

If you can and you do not have to, any answers to the following questions can help me in researching this particular issue:

What is your operating system?
Is your version of Chrome up-to-date--the newest stable release being made 4 days ago on 9-20 I believe? If not, what version are you using?
Can you reproduce the issue? If so, what exact steps cause the problem occur every time?
Does this problem only occur in Chrome? Have you tried taking the same steps that cause the problem in any other browser and if so did it cause the problem?
Are you using the quick reply or the full-editor when it occurs?
Are you just typing the smilies or are you clicking them to add them to the post?
Does the crash only occur after entering smilies or is it just usually after entering them?
Has it occurred on any other page of this website or only on the posting.php page?
Does the page come back when you hit reload?
Is what you have written in the title and post box still there when you hit reload?
What are the posting options (e.g. "disable BBCode" "disable smilies") set to when this happens?

Do not you feel you have to answer any or all of those questions. Just any of those answers may provide information to help understand and fix and/or make a work-around for this problem. If anyone else encounters repeated browser crashes on this site in particular, please tell me and you can use those same questions if you can to give me some extra potentially useful information.

Thanks again very much!
Scott