Doesn't seem that different. One thing is that Firefox would often quit on me when I had multiple tabs open which were doing a lot (like checking games on nfl.com). We'll see how that goes with Chrome.
Crashing on nfl.com is probably due to flash. As bad of a resource hog flash is on Windows, it is exponentially worse on OS X. Absolute junk. MS Silverlight on the Mac is so much better than Flash. Chrome has the sandboxing that Chief mentioned, and the newest version of Safari also has something similar that will prevent the entire browser from crashing if a plugin gets out of hand, such as flash. I don't think it is as robust as Chrome's separate process per tab method though.
One thing you might like with Chrome is that it uses Webkit as the rendering engine, so if you like the way Safari renders some sites, Chrome should render it the same since they are both based on Webkit whereas Firefox is based on Gecko. I mainly use Firefox on my Mac since I've been using it since it was called Phoenix in my PC days, but there are a few sites that don't work quite right in Firefox that I will fire up Safari to browse. Then there are those very few sites that must have IE and when changing the user agent in Firefox to IE still doesn't work, I use ies4osx to run IE7.