Browser Google Chrome

The Chrome team is delighted to announce the promotion of Chrome 41 to the stable channel for Windows, Mac and Linux. Chrome 41.0.2272.76 contains a number of fixes and improvements, including:
  • A number of new apps/extension APIs
  • Lots of under the hood changes for stability and performance
A list of changes is available in the log.

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 51 security fixes. Below, we highlight fixes that were contributed by external researchers. Please see the Chromium security page for more information.

[$7500][456516] High CVE-2015-1212: Out-of-bounds write in media. Credit to anonymous.
[$5000][448423] High CVE-2015-1213: Out-of-bounds write in skia filters. Credit to cloudfuzzer.
[$5000][445810] High CVE-2015-1214: Out-of-bounds write in skia filters. Credit to cloudfuzzer.
[$5000][445809] High CVE-2015-1215: Out-of-bounds write in skia filters. Credit to cloudfuzzer.
[$4000][454954] High CVE-2015-1216: Use-after-free in v8 bindings. Credit to anonymous.
[$3000][456192] High CVE-2015-1217: Type confusion in v8 bindings. Credit to anonymous.
[$3000][456059] High CVE-2015-1218: Use-after-free in dom. Credit to cloudfuzzer.
[$3000][446164] High CVE-2015-1219: Integer overflow in webgl. Credit to Chen Zhang (demi6od) of NSFOCUS Security Team.
[$3000][437651] High CVE-2015-1220: Use-after-free in gif decoder. Credit to Aki Helin of OUSPG.
[$2500][455368] High CVE-2015-1221: Use-after-free in web databases. Credit to Collin Payne.
[$2500][448082] High CVE-2015-1222: Use-after-free in service workers. Credit to Collin Payne.
[$2000][454231] High CVE-2015-1223: Use-after-free in dom. Credit to Maksymillian Motyl.
[449610] High CVE-2015-1230: Type confusion in v8. Credit to Skylined working with HP’s Zero Day Initiative.
[$2000][449958] Medium CVE-2015-1224: Out-of-bounds read in vpxdecoder. Credit to Aki Helin of OUSPG.
[$1000][446033] Medium CVE-2015-1225: Out-of-bounds read in pdfium. Credit to cloudfuzzer.
[$1000][456841] Medium CVE-2015-1226: Validation issue in debugger. Credit to Rob Wu.
[$1000][450389] Medium CVE-2015-1227: Uninitialized value in blink. Credit to Christoph Diehl.
[$1000][444707] Medium CVE-2015-1228: Uninitialized value in rendering. Credit to miaubiz.
[$500][431504] Medium CVE-2015-1229: Cookie injection via proxies. Credit to iliwoy.

We would also like to thank all security researchers that worked with us during the development cycle to prevent security bugs from ever reaching the stable channel. The total value of additional rewards and their recipients will be updated here when all reports have gone through the reward panel.

As usual, our ongoing internal security work was responsible for a wide range of fixes:
  • [463349] CVE-2015-1231: Various fixes from internal audits, fuzzing and other initiatives.
  • Multiple vulnerabilities in V8 fixed at the tip of the 4.1 branch (currently 4.1.0.21).

Many of the above bugs were detected using AddressSanitizer or MemorySanitizer.

The dev channel has been updated to 42.0.2311.15 for Windows, Mac and Linux.

A list of changes is available in the log.

Cumprimentos. :D
 
É só a mim que ao abrir a página da google, o browser fica ali a carregar tempos infinitos até levar com o erro de que a página deixou de responder? Isto tanto me acontece como não e foi de repente. É que se eu abrir outra página qualquer que seja, zero problemas... Mas se abrir o google.pt/com simplesmente não abre a página, fica ali a carregar. Se abrir a página noutro browser, abre sem problemas... wtf?

Nesto último update tenho um problema parecido mas acontece em qualquer site e em páginas aleatórias. Até acontece quando abre aqui o fórum. Tipo, fica ali a engonhar, parece que não carrega a página, algumas ficam todas desorganizadas e por vezes pede-me para gravar o .html no computador em vez de mostrar o site.
 
De volta ao Chrome após uns meses usando Firefox* e uns dias usando IE11**

* acho que os vídeos do Youtube correm melhor no meu netbook usando o Chrome.

** não acho o Internet Explorer 11 tão mau como muita gente diz mas, lá está, preciso dos vídeos no netbook.
 
De volta ao Chrome após uns meses usando Firefox* e uns dias usando IE11**

* acho que os vídeos do Youtube correm melhor no meu netbook usando o Chrome.

** não acho o Internet Explorer 11 tão mau como muita gente diz mas, lá está, preciso dos vídeos no netbook.

Eu aqui no Ubuntu uso Chrome, tenho o firefox instalado, mas acho-o mais lento (muito mais).
O IE11 safa-se para pequenas coisas, também já tive o vivaldi, midori, etc.

Acabo sempre por ir para o chrome por ter a integração e «funcionar» com o youtube.

Eu ativei o SPDY/4 (http/2) para ser mais rápido, nas flags do chrome, apesar disso, para já não noto diferenças significativas.
 
The Chrome engineering team is excited to announce the promotion of Chrome 42 to the beta channel for Windows, Mac and Linux. Chrome 42.0.2311.22 contains many improvements including:


A full list of changes in this build is available in the log. Find out more at the Chrome andChromium blogs.

The stable channel has been updated to 41.0.2272.89 for Windows, Mac and Linux. A full list of changes is available in the log.

The dev channel has been updated to 43.0.2327.5 for Windows, Mac, and Linux.

A list of changes is available in the log.

Cumprimentos. :D
 
Tenho a beta e desde a última atualização que não consigo activar o Flash externo, só o pepper que no meu PC é lento como tudo... Mais alguém nesta situação?

Porcaria de browser... E o pior é que as alternativas não são melhores... Saudades do antigo opera....
 
Tenho a beta e desde a última atualização que não consigo activar o Flash externo, só o pepper que no meu PC é lento como tudo... Mais alguém nesta situação?

Porcaria de browser... E o pior é que as alternativas não são melhores... Saudades do antigo opera....

Já vi que eles vão deixar de ter suporte a NPAPI, vamos ser obrigados a usar os plugins internos. Embora perceba os motivos, não acho bem forçarem esta mudança tendo em conta a performance miserável que o flash PPAPI tem.

Isso da RAM é outra questão, come mesmo muita... Eu quando venho aqui ao fórum e quero abrir os tópicos subscritos por ler (normalmente +20 tabs), uso o Opera 12, porque com o Chrome é impossível, com 5 ou 6 tabs já me deixa o PC de rastos.
 
Estranho, eu em OS X usava o Firefox porque achava que o Chrome consumia imensa memória, só que passadas algumas horas o FF fica super lento nos retina Macs. Mudei para o Chrome de novo (já tinha usado durante muito tempo, mas depois mudei para o FF), e esta lentidão não acontece. Gasta é mais bateria, mas usar o Safari não é opção.
 
The dev channel has been updated to 43.0.2334.0 for Windows, Mac, and Linux.

A list of changes is available in the log.

The beta channel has been updated to 42.0.2311.50 for Windows, Mac and Linux.

A list of changes is available in the log.

The stable channel has been updated to 41.0.2272.101 for Windows, Mac and Linux. A partial list of changes is available in the log.

Cumprimentos. :D
 
The stable channel has been updated to 41.0.2272.118 for Windows, Mac and Linux. A partial list of changes is available in the log.
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 4 security fixes. Below, we highlight fixes that were contributed by external researchers. Please see the Chromium security page for more information.
[$29633.7][469058] Critical CVE-2015-1233: A special thanks to Anonymous for a combination of V8, Gamepad and IPC bugs that can lead to remote code execution outside of the sandbox.
[468936] High CVE-2015-1234: Buffer overflow via race condition in GPU. Credit to lokihardt working with Pwn2Own and HP’s Zero Day Initiative.

The beta channel has been updated to 42.0.2311.68 for Windows, Mac and Linux.

A list of changes is available in the log.

Cumprimentos. :D
 
The Chrome team is overjoyed to announce the promotion of Chrome 42 to the stable channel for Windows, Mac and Linux. Chrome 42.0.2311.90 contains a number of fixes and improvements, including:


A list of changes is available in the log.

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 45 security fixes. Below, we highlight fixes that were contributed by external researchers. Please see the Chromium security page for more information.

[$7500][456518] High CVE-2015-1235: Cross-origin-bypass in HTML parser. Credit to anonymous.
[$4000][313939] Medium CVE-2015-1236: Cross-origin-bypass in Blink. Credit to Amitay Dobo.
[$3000][461191] High CVE-2015-1237: Use-after-free in IPC. Credit to Khalil Zhani.
[$2000][445808] High CVE-2015-1238: Out-of-bounds write in Skia. Credit to cloudfuzzer.
[$1000][463599] Medium CVE-2015-1240: Out-of-bounds read in WebGL. Credit to w3bd3vil.
[$1000][418402] Medium CVE-2015-1241: Tap-Jacking. Credit to Phillip Moon and Matt Weston of Sandfield Information Systems.
[$500][460917] High CVE-2015-1242: Type confusion in V8. Credit to [email protected].
[$500][455215] Medium CVE-2015-1244: HSTS bypass in WebSockets. Credit to Mike Ruddy.
[$500][444957] Medium CVE-2015-1245: Use-after-free in PDFium. Credit to Khalil Zhani.
[$500][437399] Medium CVE-2015-1246: Out-of-bounds read in Blink. Credit to Atte Kettunen of OUSPG.
[$500][429838] Medium CVE-2015-1247: Scheme issues in OpenSearch. Credit to Jann Horn.
[$500][380663] Medium CVE-2015-1248: SafeBrowsing bypass. Credit to Vittorio Gambaletta (VittGam).

We would also like to thank all security researchers that worked with us during the development cycle to prevent security bugs from ever reaching the stable channel. The total value of additionalrewards and their recipients will updated here when all reports have gone through the reward panel.
As usual, our ongoing internal security work was responsible for a wide range of fixes:
[476786] CVE-2015-1249: Various fixes from internal audits, fuzzing and other initiatives.
Multiple vulnerabilities in V8 fixed at the tip of the 4.2 branch (currently 4.2.77.14).
Many of the above bugs were detected using AddressSanitizer or MemorySanitizer.

The dev channel has been updated to 43.0.2357.18 for Windows, Mac, and Linux.

A list of changes is available in the log.

Cumprimentos. :D
 
Back
Topo