I think i found the cause of it (Airport) and made a video:
http://www.youtube.com/watch?v=flT7U_kGpaM
http://www.youtube.com/watch?v=flT7U_kGpaM
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Apple's New 27-Inch iMacs Experiencing Performance Issues?
- Thread starter MacRumors
- Start date
- Sort by reaction score
If you click on the video provided in the article, the guy posted a follow-up video showing how to fix it.
I find it ironic that he chose to show how to fix the problem while playing back one of those smug-ass "I'm a Mac" commercials where the woman talks about wanting a computer that "just works," while the guy watching the video on his "just working" computer has to turn off wireless and turn it back on just to get simple internet videos to play correctly.
I find it ironic that he chose to show how to fix the problem while playing back one of those smug-ass "I'm a Mac" commercials where the woman talks about wanting a computer that "just works," while the guy watching the video on his "just working" computer has to turn off wireless and turn it back on just to get simple internet videos to play correctly.
You cannot be positive because you 100% wrong. THIS IS NOT ADOBE'S FAULT. THIS IS APPLE! Flash causing the slowdown is only a symptom of a deeper problem! Do you people realize that this can also be set off by playing 3D games and not using Flash AT ALL? It is a problem with the 4670 driver and the Airport driver. Don't ask me how, but are you all so quick to forget the lockups that happened when the 4850s came out? Remember the workaround? Turning off Airport fixed it until Apple issued a firmware update. This is nearly the same thing! But the fanboys will continue to bash Adobe (yes, Flash sucks, but not like you think in this particular case) because you don't have all the information and you're kneejerking in defense of Apple. You can cause this problem without ever loading a scrap of Flash code. Ergo, it is an Apple problem.
Bottom line: When you can cause the problem without Flash, then Flash is not the issue. A lot of people in this thread really need to get their heads out of their asses and point the finger where it needs to go: Squarely at Apple.
However, Microsoft continues to support and develop Win32, even on Windows 7 x64 systems. Apple dropped Carbon64 from its plans,
Microsoft has also responded to the complaints about forcing a .NET transition, and is actively developing native (non-managed) interfaces and run-times in parallel with .NET. For example, the new ConcRT (Concurrency Runtime) threading package is available for native C++ code.
Win32 is alive and well in both 32-bit and 64-bit flavors. Microsoft is moving to the name "Windows API" (http://en.wikipedia.org/wiki/Windows_API) and isn't using the "Win64" name. (Makes sense - since Win64 isn't a different API from Win32 - it's just Win32 in LLP64 mode.) So, "Win64" is an informal shorthand for "Windows API 64-bit", and a few compiler switches and macros.
Maybe Apple is subtly hinting that we should all stop using Flash? First no flash support on the iPhone, now bad support on SL.
~Callum
~Callum
That's a heck of a way to do it. Making video run like trash on a $2000 computer....which you find out AFTER you buy it.
LOL
Yeah, I'm getting that and I have no intention to descend into a fanboy tussle with him or anyone else.
The simple fact is that nobody has any idea yet if this is the fault of Apple or Adobe or some combination of both (which is entirely possible too--nobody should rule out a subtle weakness in the OS being exacerbated by skanky programming--wouldn't be the first time Apple and Adobe have joined forces to create such a problem.) Anyone defending one side or the other is filtering all the evidence out there to support their own bias.
And as far as I'm concerned, that's the very definition of fanboy.
Nice rant. Problem is that Adobe is gaining a lot of well-deserved notoriety for their lousy programming. It is entirely within the realm of possibility that Adobe and others are using APIs or libraries that Apple has deprecated or asked developers to replace or abandon. All it takes is for Apple to let things lag in their support for old libraries, and for developers to have a lazy streak, and you get this kind of crap happening. In that situation, it would be both parties that are to fault. It's a lot more complicated than pointing the finger one way or the other.
Problem Solved
This is a post on the Apple Support forum that seems to be working for all those having this problem.
SOLVED: iMac 27'' (Late 2009) Poor Performance and Flash Issues w/ SOLUTION
Posted: Oct 31, 2009 1:50 AM
Reply Email
I was able to cure all my performance issues by doing a low-level power/video/parameter reset (NVRAM/PRAM) to my iMac 27'' / 3.0Ghz / 4GB / ATi Radeon HD 4670 256MB
I had the following symptoms:
Ridiculous boot time (5-6 minutes)
Sluggish behavior in all window-based operations (hide/show/open apps; switch apps; open new windows, docs, etc.)
Abhorrent Flash performance (even worse than usual for Flash)
Xbench score = 124.22 (pathetic)
Steps to cure:
1) Shutdown iMac
2) Unplug power cord from back of iMac
3) Press and hold power button for 20 seconds
4) Restore power cord; power on iMac
5) Immediately on hearing Startup Chime, press and hold Command-Option-P-R keys (⌘⌥ P R)
6) Wait until you hear an additional four (4) chimes; the fourth (fifth) chime will (should) be louder and clearer
7) Release the keys and allow iMac to boot normally.
Note: This reboot may take up to two minutes, but subsequent reboots should be less than 30-45 seconds.
Results:
Boot time 35 seconds
super snappy app/window behavior (especially Parallels/Windows and Safari/Flash
New Xbench Score = 286.24 (must admit I thought this would be higher)
Super Happy owner of the hands-down, most kickass screen on the planet
HTH
Frederico
Message was edited by: Frederico
Mac Pro Quad 2.8/6GB/ATi HD 2600 x 3/ 5 LCD Displays Mac OS X (10.6.1) iMac 27'' / 3.0Ghz / 4GB / ATi Radeon HD 4670 256MB
This is a post on the Apple Support forum that seems to be working for all those having this problem.
SOLVED: iMac 27'' (Late 2009) Poor Performance and Flash Issues w/ SOLUTION
Posted: Oct 31, 2009 1:50 AM
Reply Email
I was able to cure all my performance issues by doing a low-level power/video/parameter reset (NVRAM/PRAM) to my iMac 27'' / 3.0Ghz / 4GB / ATi Radeon HD 4670 256MB
I had the following symptoms:
Ridiculous boot time (5-6 minutes)
Sluggish behavior in all window-based operations (hide/show/open apps; switch apps; open new windows, docs, etc.)
Abhorrent Flash performance (even worse than usual for Flash)
Xbench score = 124.22 (pathetic)
Steps to cure:
1) Shutdown iMac
2) Unplug power cord from back of iMac
3) Press and hold power button for 20 seconds
4) Restore power cord; power on iMac
5) Immediately on hearing Startup Chime, press and hold Command-Option-P-R keys (⌘⌥ P R)
6) Wait until you hear an additional four (4) chimes; the fourth (fifth) chime will (should) be louder and clearer
7) Release the keys and allow iMac to boot normally.
Note: This reboot may take up to two minutes, but subsequent reboots should be less than 30-45 seconds.
Results:
Boot time 35 seconds
super snappy app/window behavior (especially Parallels/Windows and Safari/Flash
New Xbench Score = 286.24 (must admit I thought this would be higher)
Super Happy owner of the hands-down, most kickass screen on the planet
HTH
Frederico
Message was edited by: Frederico
Mac Pro Quad 2.8/6GB/ATi HD 2600 x 3/ 5 LCD Displays Mac OS X (10.6.1) iMac 27'' / 3.0Ghz / 4GB / ATi Radeon HD 4670 256MB
So, as my post above shows, it basically requires a reset / reboot to fix it.
So how many times a day do you have to reboot your netbook and don't you wish you could fix Windows problems with a reboot. I haven't rebooted my macbook since I upgraded to SL.
Like I said, the problem can occur without ever using Flash in any capacity. Playing WoW for 20 minutes or so sets it off. Is Blizzard at fault too? When multiple unrelated apps can cause the issue and resetting Airport fixes it, then the fault lies with Apple, plain and simple.
If you take the red pill, it's all Apple's fault. You can go back to believing Windows rules the world by virtue of its perfection and that Steve Jobs is a hippie megalomaniac leading the clueless masses... and everything will be fine.
If you take the blue pill, Adobe is to blame. You can go back to believing Apple rules the world and that Steve Jobs has descended from on-high from the very hand of God to create worldwide peace and love... and everything will be fine.
But either way, you're just another @#$%&* pill-head.
Discrete 9400GT card? Ummm nope. Try 9400m Integrated card! If you have a 9600 card then that is discrete, but I can assure you the 9400s in MBs and MBPs are integrated 9400m chips
Actually it also seems to affect new imacs with the 4850 too (mine has one and Im getting the problem too....). Oh and yes it's not just Flash, pretty much everything slows down...untill I turn off the airport....so weird
If you take the red pill, it's all Apple's fault. You can go back to believing Windows rules the world by virtue of its perfection and that Steve Jobs is a hippie megalomaniac leading the clueless masses... and everything will be fine.
If you take the blue pill, Adobe is to blame. You can go back to believing Apple rules the world and that Steve Jobs has descended from on-high from the very hand of God to create worldwide peace and love... and everything will be fine.
But either way, you're just another @#$%&* pill-head.
=)
Brilliant bit of troubleshooting and deduction there. Of course you had a headstart knowing, a priori, that it can't possible be Apple's fault. Maximum Reality Distortion Field demo. Thanks !
If anything, it's LTD, what's new?
How can you be sure? If Blizzard is slow to update their code, we could be seeing the same thing there too. I'm not saying Apple's off the hook because they've been known to let their older libraries and APIs languish but if Blizzard and Adobe both linger and refuse to update their programs in a timely manner, that means they share some of the blame too.
And if you've ever done any development, you'd know that it's very complicated and just because resetting Airport fixes it doesn't definitively prove anything.
In any case, you should ask yourself why you're so convinced it's one party to blame over the other... even before Apple's own engineers have figured it out. Examine your own biases for a moment. Think about how complicated this stuff gets and ask yourself why you would blame either side at this stage.
Meanwhile, I'll be thanking god that you're not a judge.
It's a pity Adobe have allowed their software to fall down like this. In the right hands Flash has no competition.
