(Credit:
CNET)
Last month we blogged about a bug marring Flash playback on the latest 27-inch Apple iMacs. Users on several Web sites, including the Apple Discussion Threads, noticed a problem with the Flash player that caused choppy audio and video playback, but it appears that the newest Mac OS X v10.6.2 update fixes the issue that was apparently caused by a conflict with the Airport driver.
According to Apple, the update "addresses video playback and performance issues for iMac (21.5-inch, late 2009) and iMac (27-inch, late 2009) computers that may occur in some situations while AirPort is turned on." Since our own 27-inch iMac also experienced slow Flash streaming and intermittent sound hiccups with the AirPort turned on, we downloaded the 10.6.2 update and left it to sleep overnight.
Prior to the update, the Flash Player consumed 114.4 percent of system resources, but 24 hours after the update we're happy to report 26.8 percent usage in the activity monitor and smooth performance across all popular streaming video Web sites like YouTube, Hulu, etc.
Much thanks to the Apple Forums and Apple itself for quickly addressing the needs of its community. If you haven't updated yet, simply choose Software Update from the Apple menu to install OS X v10.6.2.
(Credit:
CNET)
After reading Engadget's report citing recent complaints about Flash video playback mucking up system resources on the latest 27-inch Apple iMacs, we decided to test out the claims using our own system. Users on the Apple Discussion threads noticed a bug in the Flash Player that bogs down CPU processes, resulting in choppy audio and video playback.
We visited several sites with heavy streaming video content like Hulu, YouTube, and the Break Media Network, and experienced similar issues: popping sounds and jerky video rendering the content unwatchable on several accounts. Like many of the users in the Apple thread, we called up the Activity Monitor and saw that the Flash Player demanded a surprising 114.4 percent of the iMac's CPU processes.
We were able to temporarily fix the problem by putting the computer to sleep and waking it up, but some people are speculating that a hardware malfunction could be to blame. We've also tried to contact Apple for official word, but our messages have been as yet unreturned.
If you're experiencing similar problems, we'd like to hear about it--leave a comment and let us know the issue and what you did to fix it.
- prev
- 1
- next
