crashgoogle-chrome
Every time I launch Chromium, a dialog box appears almost immediately telling me that "Chromium Helper EH has unexpectedly quit." Several things don't work, including the New Tab button missing the + symbol, several keyboard shortcuts don't work, and pages don't load more than halfway. What's happening and how can I fix it?
(Extra phrases to help this show up for people searching for "Google Chrome": Google Chrome Helper EH, Google Chrome crashes.)
It’s a typical BAD_EXEC. This could be related to two main things:
A bug in the program. The Mac programming framework (Called Cocoa) and the programming language used to develop most Mac programs (Objective-C) are very tricky with memory handling. A simple mistake could lead to unpredictable and unexpected crashes that seem to follow no “pattern”. It’s very common, it happens in the best software shops and until the vendor fixes the memory leak, there is nothing you can do (other than send them the bug report and pray).
If this behavior is exhibited by more software, there might be a problem with your hardware memory (RAM). Faulty RAM sticks are know to have caused this type of errors in a more or less unpredictable way. Programs start crashing and with time, new ‘problems’ arise, until the machine might eventually become almost unusable.
What can you do?
A simple test may be conducted by creating a new blank user in your computer, restarting your computer and using Messenger from the new user. This will rule any possible software problem with your user. If Messenger works fine under the new account, then further analysis of yours will lead us to try to find what’s interfering with MSN.
If it fails to work under the new account too, then the problem lies either in the MSN, Your OS X in general (weird but possible, usually a new user fixes 90% of the problems), or, worst case scenario, in your Hardware.
I suggest you try to above and take an action course. As a last resort, don’t hesitate taking the machine to an Apple Store/Genius Bar for further analysis. They will be able to provide you with much more information that what we could from here.
It's a bug in 10.8.1 and 10.8.2 only.
The workaround for this pesky bug is to disable two items in Language & Text Preference Pane in System Preferences on affected versions of Mountain Lion:
Credit for this workaround goes to user shess on the open radar web site.
Best Answer
It turns out that in 10.7.3, installing Chromium/Google Chrome from another account causes this bug. Simply installing it while using the account it will be used in solves the problem. Unfortunately, no other accounts can use it.