Tumblr 101: Tips And Tricks To Get Started
WATCH: Shredding On The Google Guitar!
Internal Flash plugin integration hits Google Chrome
If you've already got the build installed, you need to add a command line switch to enable the magic: --enable-internal-flash. Need help adding the switch? Check our tutorial post for more details.
Once the switch has been flipped, you'll see the confirmation dialog pictured above. There seem to be some performance benefits to the internal plugin -- the HD clip I tested on YouTube never reached more than 19% CPU utilization.
According to Adobe, "Moving forward, Google will be including Flash Player in Chrome so users will always have the most current release and a safer and more seamless experience." As I mentioned earlier, it makes sense for Google to start bundling the internal plug-in for a number of reasons. The internal plug-in will also automatically update itself using Chrome's built-in mechanism, eliminating the need for out-of-browser Flash updating.
The official Adobe post concludes by saying, "Our hope is that the robust integration between Chrome and Flash Player will serve as a showcase for more consistent, seamless, and efficient Web browsing experiences. We feel that this significant effort by both Google and Adobe will directly improve the speed of innovation and move the Web forward, benefiting the entire community of developers and end-users."
CPU and memory usage while watching an HD clip on YouTube with the internal Flash plugin enabled.
Comments
6
Subscribe to commentsRogueJedi86Mar 30th 2010 2:53PM
Does this mean Flash Player will no longer show up as its own process in the Chrome Task Manager? It's always the Chrome Task that hogs up the most CPU when I run Chrome. And with that, does that mean Flash can no longer crash without taking down the rest of Chrome with it? It's always been convenient that if Flash crashes in Chrome, the browser is intact and I can just refresh a tab to reload Flash. So many questions.....
NickMar 30th 2010 4:43PM
It still shows a "Plug-in: Shockwave Flash" when I use the new plugin
RogueJedi86Mar 30th 2010 4:46PM
You can force a Flash crash if you end the process in the Chrome Task Manager. Since you're on the dev build, you could close it that way and see if it does anything besides the "The following plugin has crashed" message along the top of the browser.
mrickMar 30th 2010 4:23PM
I think the idea is that Flash will eventually run sandboxed inside of Chrome. That should make using Flash more secure in the browser and also leave Chrome intact if Flash misbehaves.
Tired_Mar 30th 2010 11:22PM
What if I wanna run a beta version of Flash?
RobomasterMar 31st 2010 9:27AM
It seems you can't use a Flash beta anymore - they'll add a stable one automatically. Google might add options to configure this (and add a beta) but I doubt it.