The worst version from the beginning of Iron! For first time I had to downgrade. Almost everything doesn't work. Timers in inactive pages are slowing down (alot), this began from 27.0, but now it like hell! Even simplest Facebook application and games doesn't work at all. The best version at this point for me is 26.0.

I can go on a twitter profile with a Google's research (example "Obama twitter") but when I am on the profile, it does not anything when I click on "Login", or "open" (a tweet), or any other clickable button...

A bit of an update, I've updated my GT9600M GeForce drivers to the latest and Iron doesn't crash as often so I will keep this in mind from now on seeing as Nvidia has had a lot of Driver problems lately.

Also the crashes seem to happen while on CrapTube the ram useage shoots up and causes Iron to crash so hard that restoring tabs doesn't work and the history is also flushed out so no way of getting back to site that were open.

SRWare.net could you please enable a function of loading active tabs only, this was an excellent way of starting Iron where inactive tabs are not loaded until selected.

in the latest version is there anyway to disable the automatic google search of anything in the address bar? Are all these searches submitted to google. Also does the program really call home when clikcing on about/iron.

New "Stable Channel UpdateChrome has been updated to 31.0.1650.48 for Windows, Mac, Linux and Chrome Frame.

Flash Player has been updated to 11.9.900.152, which is included w/ this release.

Security Fixes and Rewards

Note: Access to bug details and links may be kept restricted until a majority of users are updated with a fix. We will also retain restrictions if the bug exists in a third party library that other projects similarly depend on, but haven’t yet fixed.

This update includes 25 security fixes. Below, we highlight fixes that were either contributed by external researchers or particularly interesting. Please see the Chromium security page for more information.

[$500][268565] Medium CVE-2013-6621: Use after free related to speech input elements. Credit to Khalil Zhani.[$2000][272786] High CVE-2013-6622: Use after free related to media elements. Credit to cloudfuzzer.[$500][282925] High CVE-2013-6623: Out of bounds read in SVG. Credit to miaubiz.[$1000][290566] High CVE-2013-6624: Use after free related to “id” attribute strings. Credit to Jon Butler.[$2000][295010] High CVE-2013-6625: Use after free in DOM ranges. Credit to cloudfuzzer.[295695] Low CVE-2013-6626: Address bar spoofing related to interstitial warnings. Credit to Chamal de Silva.[$4000][299892] High CVE-2013-6627: Out of bounds read in HTTP parsing. Credit to skylined.[$1000][306959] Medium CVE-2013-6628: Issue with certificates not being checked during TLS renegotiation. Credit to Antoine Delignat-Lavaud and Karthikeyan Bhargavan from Prosecco of INRIA Paris.

We would also like to thank miaubiz and Atte Kettunen of OUSPG for working with us during the development cycle to prevent security bugs from ever reaching the stable channel. $2000 in additional rewards were issued.

As usual, our ongoing internal security work responsible for a wide range of fixes:

[315823] Medium-Critical CVE-2013-2931: Various fixes from internal audits, fuzzing and other initiatives. [258723] Medium CVE-2013-6629: Read of uninitialized memory in libjpeg and libjpeg-turbo. Credit to Michal Zalewski of Google. [299835] Medium CVE-2013-6630: Read of uninitialized memory in libjpeg-turbo. Credit to Michal Zalewski of Google. [296804] High CVE-2013-6631: Use after free in libjingle. Credit to Patrik Höglund of the Chromium project."

How manu week need in team SRWare Iron to made New Version ? And Please Stop send info to Google to be good privacy and safe to use your browser!