I had the same problem on chrome. There's a lengthy bug discussion and a suggested solution (that worked for me): https://code.google.com/p/chromium/issues/detail?id=175341#c...
The immediate difference toggling "Predict network actions to improve page load performance" off for me is STUNNING. Thank you so much.
Re:Why I'm switching back to Firefox
by AlexeyBrin on Monday March 11, 2013 @09:53AM
(#5356644)
I've had the same problem with Chrome on ML, reinstall the browser and the bug will disappear (you'll need to erase it from your Applications and from ~/Library/Caches).
Re:Why I'm switching back to Firefox
by JonnieCache on Monday March 11, 2013 @07:04AM
(#5355962)
FWIW It's stopped doing that to me in recent weeks.
When you're not logged into your google account, typing into the address bar with periodically kill chrome on mountain lion.
Not often, but maybe 3 or 4 times a day. Not kill the tab; hard kill chrome, instantly, destroying all the tabs, no recovery, all chrome processes go poof. It happens on all three of my mac devices (and this is on Version 25.0.1364.160).
It's not even a choice; that's just unusable.
I've also found firefox to be a lot better than I remember. Firebug is still a memory hog though, and as we saw in the other epic thread, the firebug / native developer tools thing is still just idiotic.
...but it's pretty good.
I honestly didn't expect to be ever returning to firefox because it was more stable than the alternative.