Browser Google Chrome

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

A partial list of changes is available in the log.

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


A partial list of changes is available in the log.

The stable channel has been updated to 54.0.2840.99 for Windows, 54.0.2840.98 for Mac, and 54.0.2840.100 on Linux. This will roll out over the coming days/weeks.

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 Chrome Security Page for more information.
[$5500][643948] High CVE-2016-5199: Heap corruption in FFmpeg. Credit to Paul Mehta
[$5000][658114] High CVE-2016-5200: Out of bounds memory access in V8. Credit to Choongwoo Han
[$1000][660678] Medium CVE-2016-5201: Info leak in extensions. Credit to Rob Wu
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.
As usual, our ongoing internal security work was responsible for a wide range of fixes:
  • [662843] CVE-2016-5202: Various fixes from internal audits, fuzzing and other initiatives
Many of our security bugs are detected using AddressSanitizer, MemorySanitizer, Control Flow Integrity, or libFuzzer.

A list of changes is available in the log.

Cumprimentos :D
 
Boa tarde,

Uso o Chrome portable Versão 54.0.2840.99 no work, quando quero repor os separadores gravados no histórico do chrome portable no PC pessoal, não aparecem os separadores todos.

Alguém teve um problema parecido?
 
The dev channel has been updated to 56.0.2924.10 for Windows, Mac, and Linux.

A partial list of changes is available in the log.

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


A partial list of changes is available in the log.

The Chrome team is delighted to announce the promotion of Chrome 55 to the stable channel for Windows, Mac and Linux. This will roll out over the coming days/weeks.

Chrome 55.0.2883.75 contains a number of fixes and improvements -- a list of changes is available in the log. Watch out for upcoming Chrome and Chromium blog posts about new features and big efforts delivered in 55.
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 36 security fixes. Below, we highlight fixes that were contributed by external researchers. Please see the Chrome Security Page for more information.
[$N/A][664411] High CVE-2016-9651: Private property access in V8. Credit to Guang Gong of Alpha Team Of Qihoo 360
[$7500][658535] High CVE-2016-5208: Universal XSS in Blink. Credit to Mariusz Mlynski
[$7500][655904] High CVE-2016-5207: Universal XSS in Blink. Credit to Mariusz Mlynski
[$7500][653749] High CVE-2016-5206: Same-origin bypass in PDFium. Credit to Rob Wu (robwu.nl)
[$7500][646610] High CVE-2016-5205: Universal XSS in Blink. Credit to Anonymous
[$7500][630870] High CVE-2016-5204: Universal XSS in Blink. Credit to Mariusz Mlynski
[$5000][664139] High CVE-2016-5209: Out of bounds write in Blink. Credit to Giwan Go of STEALIEN
[$3000][644219] High CVE-2016-5203: Use after free in PDFium. Credit to Anonymous
[$3500][654183] High CVE-2016-5210: Out of bounds write in PDFium. Credit to Ke Liu of Tencent's Xuanwu LAB
[$3000][653134] High CVE-2016-5212: Local file disclosure in DevTools. Credit to Khalil Zhani
[$3000][649229] High CVE-2016-5211: Use after free in PDFium. Credit to Anonymous
[$500][652548] High CVE-2016-5213: Use after free in V8. Credit to Khalil Zhani
[$N/A][601538] Medium CVE-2016-5214: File download protection bypass. Credit to Jonathan Birch and MSVR
[$3000][653090] Medium CVE-2016-5216: Use after free in PDFium. Credit to Anonymous
[$3000][619463] Medium CVE-2016-5215: Use after free in Webaudio. Credit to Looben Yang
[$2500][654280] Medium CVE-2016-5217: Use of unvalidated data in PDFium. Credit to Rob Wu (robwu.nl)
[$2000][660498] Medium CVE-2016-5218: Address spoofing in Omnibox. Credit to Abdulrahman Alqabandi (@qab)
[$1500][657568] Medium CVE-2016-5219: Use after free in V8. Credit to Rob Wu (robwu.nl)
[$1000][660854] Medium CVE-2016-5221: Integer overflow in ANGLE. Credit to Tim Becker of ForAllSecure
[$1000][654279] Medium CVE-2016-5220: Local file access in PDFium. Credit to Rob Wu (robwu.nl)
[$500][657720] Medium CVE-2016-5222: Address spoofing in Omnibox. Credit to xisigr of Tencent's Xuanwu Lab
[$N/A][653034] Low CVE-2016-9650: CSP Referrer disclosure. Credit to Jakub Żoczek
[$N/A][652038] Low CVE-2016-5223: Integer overflow in PDFium. Credit to Hwiwon Lee
[$N/A][639750] Low CVE-2016-5226: Limited XSS in Blink. Credit to Jun Kokatsu (@shhnjk)
[$N/A][630332] Low CVE-2016-5225: CSP bypass in Blink. Credit to Scott Helme (@Scott_Helme, scotthelme.co.uk)
[$N/A][615851] Low CVE-2016-5224: Same-origin bypass in SVG. Credit to Roeland Krak
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.
As usual, our ongoing internal security work was responsible for a wide range of fixes:
  • [669928] CVE-2016-9652: Various fixes from internal audits, fuzzing and other initiatives
Many of our security bugs are detected using AddressSanitizer, MemorySanitizer, Control Flow Integrity, or libFuzzer.

Cumprimentos :D
 
Boas.

Lembro-me que na altura que começaram a aparecer os vídeos FHD 60 fps no youtube, conseguia reproduzir sem quebra de frames no meu pc portatil (t9400, 4gb ddr3, gt9600 ddr3), e neste momento não consigo!!

Se usar o IE11 consigo com algumas quebras que acontecem de 5 em 5 segundos (por aí)

Se usar Chrome, completamente impossível visualizar em FHD 60FPS.

Existe aqui algo que me esteja a escapar para aumentar a 'performance'? Qual o motivo desta diferença grande entre os dois browsers?

No Task Manager, a nível de ram e cpu não chega a 50% de utlilização enquanto reproduz.

Uma coisa diferente que também me chamou a atenção tem a ver com o facto do contraste / saturação dos vídeos ser diferente em cada um dos browsers. Não deveria ser igual?

741c89e83c.jpg



Não sei se influencia, ja testei com windows 7 e 10, clean installs, drivers up to date.


cmpts
 
Eu não sei se foi desde que actualizei os drivers da minha AMD ou não, mas à uns dias para cá o meu chrome é stutter fest! Ver vídeos no youtube é impossível, vou as estatísticas para nerds e é só dropped frames. No browsing em si, em cada pagina só a fazer scroll nota-se a lag algo que por exemplo no edge não me acontece :/
 
The dev channel has been updated to 57.0.2950.4 for Mac and Linux, and 57.0.2950.4/5 for Windows.
A partial list of changes is available in the log.

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


A partial list of changes is available in the log.

The stable channel has been updated to 55.0.2883.87 for Windows and Mac on (12/09) and Linux on (12/12). This will roll out over the coming days/weeks.

A list of changes is available in the log.

Cumprimentos :D
 
Back
Topo