Recommended Posts

Beta Channel Update

The Beta channel has been updated to 21.0.1180.60 for Windows

This build should fix most of the choppy and distorted audio issues (Issue:

136624). If you've seen these issues with the Beta, please leave us an update on the bug.

If you find new issues, please let us know by filing a bug at

http://code.google.c...um/issues/entry

Karen Grunberg

Google Chrome

Source: Google Chrome Releases blog

Stable Channel Release

The Chrome team is excited to announce the release of Chrome 21 to the Stable Channel. 21.0.1180.57 for Mac and Linux. 21.0.1180.60 for Windows and Chrome Frame. Chrome 21 contains a number of new features including a new API for high-quality video and audio communication. More detailed updates are available on the Chrome Blog.

Security fixes and rewards:

Please see the Chromium security page for more detail. Note that the referenced bugs may be kept private until a majority of our users are up to date with the fix.

  • [Linux only] [125225] Medium CVE-2012-2846: Cross-process interference in renderers. Credit to Google Chrome Security Team (Julien Tinnes).
  • [127522] Low CVE-2012-2847: Missing re-prompt to user upon excessive downloads. Credit to Matt Austin of Aspect Security.
  • [127525] Medium CVE-2012-2848: Overly broad file access granted after drag+drop. Credit to Matt Austin of Aspect Security.
  • [128163] Low CVE-2012-2849: Off-by-one read in GIF decoder. Credit to Atte Kettunen of OUSPG.
  • [130251] [130592] [130611] [131068] [131237] [131252] [131621] [131690] [132860] Medium CVE-2012-2850: Various lower severity issues in the PDF viewer. Credit to Mateusz Jurczyk of Google Security Team, with contributions by Gynvael Coldwind of Google Security Team.
  • [132585] [132694] [132861] High CVE-2012-2851: Integer overflows in PDF viewer. Credit to Mateusz Jurczyk of Google Security Team, with contributions by Gynvael Coldwind of Google Security Team.
  • [134028] High CVE-2012-2852: Use-after-free with bad object linkage in PDF. Credit to Alexey Samsonov of Google.
  • [134101] Medium CVE-2012-2853: webRequest can interfere with the Chrome Web Store. Credit to Trev of Adblock.
  • [134519] Low CVE-2012-2854: Leak of pointer values to WebUI renderers. Credit to Nasko Oskov of the Chromium development community.
  • [134888] High CVE-2012-2855: Use-after-free in PDF viewer. Credit to Mateusz Jurczyk of Google Security Team, with contributions by Gynvael Coldwind of Google Security Team.
  • [134954] [135264] High CVE-2012-2856: Out-of-bounds writes in PDF viewer. Credit to Mateusz Jurczyk of Google Security Team, with contributions by Gynvael Coldwind of Google Security Team.
  • [$1000] [136235] High CVE-2012-2857: Use-after-free in CSS DOM. Credit to Arthur Gerkis.
  • [$1000] [136894] High CVE-2012-2858: Buffer overflow in WebP decoder. Credit to J?ri Aedla.
  • [Linux only] [137541] Critical CVE-2012-2859: Crash in tab handling. Credit to Jeff Roberts of Google Security Team.
  • [137671] Medium CVE-2012-2860: Out-of-bounds access when clicking in date picker. Credit to Chamal de Silva.

Many of the above bugs were detected using AddressSanitizer.

We?d also like to thank Drew Yao / Braden Thomas / Jim Smith (all Apple Product Security), Kostya Serebryany of the Chromium development community, Atte Kettunen of OUSPG and Bernhard Bauer of the Chromium development community for working with us during the development cycle and preventing security regressions from ever reaching the stable channel.

Full details about what changes are in this release are available in the SVN revision log. Interested in hopping on the stable channel? Find out how. If you find a new issue, please let us know by filing a bug.

Karen Grunberg

Google Chrome

Source: Google Chrome Releases blog

cool!! "Chrome now includes the getUserMedia API, which lets you grant web apps access to your camera and microphone without a plug-in. The getUserMedia API is the first step in WebRTC, a new real-time communications standard which aims to allow high-quality video and audio communication on the web."

before anyone jump to conclusion it need explicit permission to enable them.

Anyone else having serious problems with Facebook in the last few weeks? (dev branch) For me the Javascript stuff is almost never working and parts don't load etc.

Aye, I had those problems too. So much, in fact, that I switched to beta channel.

Beta Channel Update

The Beta channel has been updated to 21.0.1180.64 for Mac, Linux, Windows and Chrome Frame

This build fixes:

  • more of the choppy and distorted audio issues (Issue: 136624).
  • Some known crashes (Issue: 140140)
  • Japanese characters showing in Chinese font (Issue: 140432)
  • Video playback issues with flash-based sites (Issue: 139953)
  • Sync invalidation notification broken after restart (Issue: 139424)

If you find new issues, please let us know by filing a bug at http://code.google.c...um/issues/entry

Karen Grunberg

Google Chrome

Source: Google Chrome Releases blog

Beta Channel Update

The Beta channel has been updated to 21.0.1180.75 for Mac, Linux, Windows and Chrome Frame

This build fixes:

  • Flash videos not longer remaining in fullscreen when clicking a secondary monitor while the video is playing (Issue: 140366).
  • Flash video full screen displays on wrong monitor (Issue: 137523)
  • REGRESSION: Rendering difference in Chrome 21 and 22 that affected on Persian Wikipedia (Issue: 139502)
  • Some known crashes (Issues: 137498, 138552, 128652)
  • Audio objects are not "switched" immediately (Issue: 140247)
  • Print and Print Preview ignore paper size default in printer config (Issue: 135374)
  • Candidate windows is shown in wrong place in Retina display (Issue: 139108)
  • We've also fixed the issue with no webpages loading (Issue: 140982)

If you find new issues, please let us know by filing a bug at http://code.google.c...um/issues/entry

Karen Grunberg

Google Chrome

Source: Google Chrome Releases blog

Dev Channel Update

The Dev channel has been updated to 22.0.1229.0 for Windows, Mac, and Linux. A complete log of what changed can be found in the svn revision log. Instructions and download links for our different release channels are available on the Chromium wiki. If you find what you think is a new bug, please file it in our issue tracker.

Jason Kersey

Google Chrome

Source: Google Chrome Releases blog

The new menu toolbar icon landed with this build:

capture.png

^A minor yet cool change, haha. Is there any word of a better built-in download manager coming to Chrome? Perhaps something like the one in the latest Safari, like a button in the toolbar with a dropdown menu? Kinda like what they're doing in Firefox as well.

Also, I'm still hoping for Google to change the folder icon for Bookmark folders. The current one looks like a folder icon you'd expect to see in Windows 2000 and below.

Edit: They've also seemed to have changed something regarding with Font rendering. For example; The time indicators on YouTube in the player look different than before the new Dev Channel Update. I have also noticed this on Facebook on the 3 buttons in the top toolbar. These are the only places where I have noticed it so far.

Edit 2: Font rendering has changed period. Not only for those things mentioned above but font rendering in general has changed since this Dev Channel Update.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Posts

    • For the purpose that it was built for, it’s a great machine. It’s okay to own multiple machines, it’s okay for machines to be different. If every computer was the same, they’d be boring af.
    • OpenAI is rolling out a major upgrade to ChatGPT memory by Pradeep Viswanathan OpenAI is rolling out a major upgrade to ChatGPT's memory, making the system more capable, current, and scalable across long-term use. Memory allows ChatGPT to remember useful details about users, including their preferences, projects, and constraints. Instead of starting every conversation from scratch, ChatGPT can use this context to provide more relevant responses in future chats. OpenAI first launched saved memories in February 2024. That feature allowed users to explicitly ask ChatGPT to save information into its memory, such as travel plans or writing preferences. However, this system had limits because it depended heavily on users giving clear instructions to remember something. Additionally, saved memories could become stale over time. In April 2025, OpenAI expanded memory by allowing ChatGPT to reference past chat context outside the saved memories list. This was powered by a background process called “dreaming,” which automatically curates memories from chat history. This made ChatGPT better at learning from natural conversation without requiring users to manually save every detail. Today, OpenAI announced a more capable and compute-efficient memory architecture built on top of dreaming. This new system improves ChatGPT’s ability to carry forward useful context, follow user preferences, and remain accurate as time passes. According to OpenAI’s internal evaluations, the new system improves factual recall from 67.9% in 2025 to 82.8% in 2026. Preference adherence improves from 55.3% to 71.3%, while accuracy over time improves from 52.2% to 75.1%. The best part of this new system is a new memory summary page where users can review ChatGPT's memories. Users can even update details, correct information, or give instructions on what topics ChatGPT should bring up and when. This new, improved memory system is available to ChatGPT Plus and Pro users in the US starting today. It will roll out to more countries, as well as Free and Go users, in the coming weeks.
    • I work for a video production company in Australia. The camera operators shoot footage and then pass the SD card over to the editors. Much easier than handing over the entire camera. Plus, on a busy day you can hand off the SD card and then pop another in for the next shoot. Or, you might have used multiple SD cards because you need the extra space for a long shoot. I also use USB cables and wifi for transferring footage, but in many cases an SD card reader is the easiest method.
  • Recent Achievements

    • Week One Done
      Dr Jared Dental Studio earned a badge
      Week One Done
    • Week One Done
      RG INVESTMENT GROUP earned a badge
      Week One Done
    • Very Popular
      The Norwegian Drone Pilot earned a badge
      Very Popular
    • Very Popular
      s0nic69 earned a badge
      Very Popular
    • Collaborator
      Asgardi earned a badge
      Collaborator
  • Popular Contributors

    1. 1
      +primortal
      472
    2. 2
      PsYcHoKiLLa
      247
    3. 3
      Skyfrog
      79
    4. 4
      FloatingFatMan
      67
    5. 5
      Michael Scrip
      59
  • Tell a friend

    Love Neowin? Tell a friend!