Not that Shockwave hasn’t already been a resource hog, but today is especially bad. Maybe it’s a temporary incompatibility with OS X Mountain Lion or some other random issue that will (hopefully) be patched soon. But we’re suffering. Anyone else — especially those of you on other platforms — notice any Shockwave issues in Chrome?
Brought to you by