I've seen two things implicated in several google support threads about the issue. First, having both the system and google's sandboxed flash versions enabled as plugins, and second, an older version of Trusteer Rapport (typically offered by banks) was implicated.
Both may be fixed by now, but if it's still crashing, try about:plugins, enable Details at top right, and disable the system version of Flash.
I'm having the same issue, every time I need to use flash I open safari or FF. It's one of those things that I consider so strange about giant companies like Microsoft or Google, something so important it's not getting addressed
Are you on a recent MBP? I had to turn off hardware acceleration in the version of Flash that shipped with Chrome before it would act (relatively) stable.
I'm having the same issues and for that reason I've moved back to Firefox 4, since it seems to have improved quite a bit since I moved to Chrome.
What seems rather ironical is that I only started having these issues with Chrome after they added the Flash-sandbox, which was supposedly made to stop Flash from crashing the browser. With the result that Flash is always crashing the browser, something it never did before.
actually, I would believe the sandbox was added to prevent flash from accessing parts of your machine that it shouldn't be able to access.
This is not about preventing Flash from crashing, but about preventing your machine from getting owned by an exploit for one of the countless discovered and unpatched flash security flaws.
> Sometimes I think Google needs a bigger QA team
That's an understatement :)
When I visited Google Zürich (admittedly not as crucial as Mountainview) I learned that unit testing was mostly used so they had pretty red/green lines on those LCD screens in the hall, and that any dev could break the version /in production/ pretty easily with a misplaced commit...
