myGully.com

myGully.com (https://mygully.com/index.php)
-   Windows & Software (https://mygully.com/forumdisplay.php?f=61)
-   -   Diiverse Chrome Probleme von Chrome selbst erkannt....lösen?! (https://mygully.com/showthread.php?t=4492801)

zocker7 09.07.16 12:10

Diiverse Chrome Probleme von Chrome selbst erkannt....lösen?!
 
Hi
Ich hab mich mal daran gesetzt Chrome etwas näher kennen zulernen statt "nur" zu benutzen! :)
Ich bin dabei auf folgende von Google erkannte "Probleme" gestoßen wenn ich chrome://gpu eingebe:

Graphics Feature Status

Canvas: Hardware accelerated
Flash: Hardware accelerated
Flash Stage3D: Hardware accelerated
Flash Stage3D Baseline profile: Hardware accelerated
Compositing: Hardware accelerated
Multiple Raster Threads: Enabled
Native GpuMemoryBuffers: Software only. Hardware acceleration disabled
Rasterization: Hardware accelerated
Video Decode: Hardware accelerated
Video Encode: Hardware accelerated
WebGL: Hardware accelerated

Driver Bug Workarounds

clear_uniforms_before_first_program_use
disable_discard_framebuffer
exit_on_context_lost
force_cube_complete
scalarize_vec_and_mat_constructor_args
texsubimage_faster_than_teximage
use_current_program_after_successful_link

Problems Detected

Always call glUseProgram after a successful link to avoid a driver bug: 349137
Applied Workarounds: use_current_program_after_successful_link
Some drivers are unable to reset the D3D device in the GPU process sandbox
Applied Workarounds: exit_on_context_lost
TexSubImage is faster for full uploads on ANGLE
Applied Workarounds: texsubimage_faster_than_teximage
Clear uniforms before first program use on all platforms: 124764, 349137
Applied Workarounds: clear_uniforms_before_first_program_use
Always rewrite vec/mat constructors to be consistent: 398694
Applied Workarounds: scalarize_vec_and_mat_constructor_args
ANGLE crash on glReadPixels from incomplete cube map texture: 518889
Applied Workarounds: force_cube_complete
Framebuffer discarding can hurt performance on non-tilers: 570897
Applied Workarounds: disable_discard_framebuffer
Native GpuMemoryBuffers have been disabled, either via about:flags or command line.
Disabled Features: native_gpu_memory_buffers

Das sind keine wirklichen Probleme, ich weiss aber vielleicht bekommt man diese kleinigkeiten in de Griff!?
Eines davon konnte ich manuell auf Hardware Accelerated stellen : Rasterization: Hardware accelerated
Aber wie sieht mit den ganzen anderen Sachen aus?!!


Alle Zeitangaben in WEZ +1. Es ist jetzt 02:49 Uhr.

Powered by vBulletin® (Deutsch)
Copyright ©2000 - 2025, Jelsoft Enterprises Ltd.