I don't care about the FF version number, but plug-ins are required to state what versions they work with, and FF was updating more quickly than plug-in devs could keep up with. I kept having to unpack plug-ins and edit settings so they would work with the latest FF update. Too much hassle. Maybe they changed something, but I gave up.
Last I heard, the FF team made some comments that gave the impression they were giving up on the idea of separate processes per tab.
You don't need to identify Chrome processes in the Windows task manager. The separate processes already keep one tab from crashing the others (in most cases). Also, Chrome has a built-in task manager to help you identify and close a malfunctioning tab or plug-in.
I didn't mention memory issues. On my computer at work, I often find that Firefox is using > 1GB memory, even after I close all my tabs. I was using minimal plug-ins too...I'd even disable all plug-ins. This has been a frequent and consistently re-occurring problem since before FF 1.0. I used FF as my primary browser for 6+ years...but I'm done with it...unless I hear that it's using WebKit and separate processes. No going back.
They stopped that or made it a non-issue a long time ago (sometime during Firefox 4 IIRC).
Last thing I recall is that they were pushing that to a future release but its still on the table and is being tested.
I can't use Chrome when its locked up because of one tab, so there's no way I can use its management if its locked up. I've never had a tab lock up and not crash Chrome entirely, so none of that changes anything in my experience. Actually I have, but it was from a Flash plug-in crash and still locked up Chrome until it finally popped up asking if I wanted to stop it.
Flash crashes don't even crash Firefox for me so that's not any different (and its better on Firefox as it doesn't even lockup the rest of the browser, just a hiccup as every tab that had Flash kicks over and asks to reload since Flash crashed).
In Windows Task Manager it all shows up as chrome.exe and ending any one of them kills the entire Chrome process, so the separate processes didn't do anything that it was supposed to do.
In short, it operates exactly like Firefox did as far as crashing, only Chrome crashes much more. I rarely if ever have a Firefox crash any more, but Chrome does probably every couple of days if not more and I don't even do nearly as much on Chrome as I do on Firefox. On firefox I often have 50 tabs open, multiple video instances, interactive flash pages/games/etc, and a variety of other things. Half the time I even have a game (Borderland/Skyrim/Saints Row) running that I've Alt-Tab'ed out of. No problems. But I open 10 tabs in Chrome and it feels like I'm trying to play Crysis on a netbook (although its only Chrome that is functioning that way as the rest of the system is still responsive including Firefox). This is true even if Chrome is the only thing running and I just rebooted my computer.
I know you didn't, but separate processes doesn't seem to help Chrome at all and seems to cause memory issues. I think that is what is causing it to crash for me. More than a few tabs and it seems to start to bog down pretty bad and then starts trying to crash. This has happened for several releases of Chrome. I keep everything up to date (Chrome, Windows 7, plug-ins although the only plug-in I use with Chrome is AdBlock).