Here's the bug if you want to read it yourself.
And from the thread, here's how to fix it:
~$ sudo apt-get install flashplugin-installer=10.1.85.3ubuntu1 ~$ dpkg -l |egrep -i "chromium|flashp" ii chromium-browser 9.0.597.94~r73967-0ubuntu0.10.10.1 Chromium browser ii chromium-browser-inspector 9.0.597.94~r73967-0ubuntu0.10.10.1 page inspector for the chromium-browser ii chromium-codecs-ffmpeg 0.6+svn20101129r67548+69665-0ubuntu0.10.10.1 Free ffmpeg codecs for the Chromium Browser ii flashplugin-installer 10.1.85.3ubuntu1 Adobe Flash Player plugin installer
March 1 2011, 21:54:59 UTC 2 years ago
$dpkg --list | grep flash
ii flashplugin-installer 10.2.152.27ubuntu0.10.10.1 Adobe Flash Player plugin installer
$ apt-cache policy flashplugin-installer
flashplugin-installer:
Installed: 10.2.152.27ubuntu0.10.10.1
Candidate: 10.2.152.27ubuntu0.10.10.1
Version table:
*** 10.2.152.27ubuntu0.10.10.1 0
500 http://mirror.mirohost.net/ubuntu/
500 http://mirror.mirohost.net/ubuntu/
100 /var/lib/dpkg/status
10.1.85.3ubuntu1 0
500 http://mirror.mirohost.net/ubuntu/
N: Ignoring file 'old' in directory '/etc/apt/sources.list.d/' as it has no filename extension
March 2 2011, 21:14:01 UTC 2 years ago
And yes - 10.2.152.27ubuntu0.10.10.1 is the bugged version.
March 3 2011, 18:55:19 UTC 2 years ago
March 1 2011, 23:33:46 UTC 2 years ago
Either way, Chromium's been getting right on my nerves recently including a fully cross-platofrm bug in a recent build involving multiple nested divs meaning it would claim the server wasn't responding and bail.
April 19 2011, 15:40:31 UTC 2 years ago
April 19 2011, 16:21:21 UTC 2 years ago
Having read through the bug reports it can be said that it's nVidia specific but only because it's a bug in the way 32 bit Flash Player calls an nVidia specific hardware acceleration mode requesting about 1GB of VRAM which us inevitably rejected and this rejection is handled improperly (or not at all) by Flash Player.
It has also been pointed out that this is not a problem in FireFox and so may also be a bug in the way Chromium instantiates Flash.
So much as I'm sure some people would want to claim this a 'tainted driver' issue this is a dual issue involving both proprietary and opens source code.
Suspended comment