Google’s Chrome 10 browser enters beta with much faster engine, GPU support

24 Comments

“Google late Thursday posted its first public beta of Chrome 10,” Electronista reports.

“The browser is the first to use the new Crankshaft engine for JavaScript and is as much as 66 percent faster in crunching JavaScript as today’s Chrome 9,” Electronista reports. “Hardware graphics acceleration is also new and, with a fast enough system, could see as much as 80 percent of the main processor’s work offloaded to a GPU, extending the battery life on notebooks.”

Electronista reports, “The beta is available for Linux, Macs and Windows PCs.

More info and Google’s demo video in the full article here.

24 Comments

  2. I hope it handles Flash better than their last version. Of course, I’m not even gonna’ bother installing it again.

    I deleted Chrome after it crashed while visiting Digital Tutors, for like the fifth time. Honestly, even John Gruber talked up Chrome and it’s ability to handle flash content.

    At least with Safari, the Flash plug-in is all that crashes and not Safari itself. With Chrome though, it has a built-in Flash player that is about as stable as a house of cards in a wind storm.

    Reply

  3. “posted its first public beta of Chrome 10”

    And next week the first public beta of Chrome 11.
    And the week after that the public beta of Chrome 12.
    And the week after that the public beta of Chrome 13.
    …ad nauseam…

    *Don’t Care*

    Reply

    1. I’m willing to bet that you have a flaky Safari extension running. Apple have received plenty of complaints. If an extension is poorly programmed it can make Safari incredibly unstable. Go into the Preferences and play around with turning them off one at a time. (Déja vu old Mac OS). Ideally Apple should sandbox each extension, but they aren’t.

      Reply

  13. I ran into this after updating to the most recent version of the Shockwave Player. Thank Adobe for the problem and Google for not being obvious about changes they make at YouTube. Here’s what’s going on:

    1) YouTube are offering videos on their site these days in .SWF format, which does NOT use the Flash Player, but the Shockwave Player.

    2) You’ve got a mismatched bit version of Shockwave Player. Adobe warn you about this in one direction but not the other. You must match up the 32-bit version of Shockwave with running Safari in 32-bit mode. You can do this in Safari’s get info box. OR, you must match up the 64-bit version of Shockwave with running Safari in 64-bit mode.

    This is a very recent problem because dumbass Adobe have dragged their feet for nearly 6 (SIX!) years updating their Mac software to 64-bit, despite the fact that Macs went entirely 64-bit capable in 2006. Meanwhile, Adobe went 64-bit for Windows, and only an estimated 20% use 64-bit Windows. (0_o) Stupid Adobe. Idiot Adobe. Bad Adobe.
    😳

    Reply

  14. Anybody else experience Safari not closing tabs down despite repeatedly clicking the little x in the tab?
    Also in Safari, anyone else experience opening multiple tabs contained in a book mark folder and have them all stall out and run the little turning gear icon endlessly in all the tabs, even as the up and download flow has fallen to near zero?

    Reply

Reader Feedback

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Tags: , ,