Chrome and Chromium 56 crashing with hardware acceleration constantly
Reported by
quanto...@gmail.com,
Mar 10 2017
|
|||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36 Steps to reproduce the problem: 1. Browse normally 2. browser completely locks up, drops to 0 percent CPU and memory 3. kill task for chrome or chromium and restart it What is the expected behavior? not to hang. What went wrong? Doesn't matter if I'm using Windows 10 or Debian, Ubuntu, Arch, anything... if I turn on hardware acceleration the browser will completely freeze and drop to 0% CPU and 0% memory usage and be completely unresponsive. Turning OFF hardware acceleration fixes this issue, but of course then every single page or video you watch has extreme video tearing to the point it's absolutely useless as a web browser. Surely with all the other people complaining about this same issue that someone is working on a fix? previous versions of Chrome were fine. Current OS: Ubuntu Chrome Browser: Version 56.0.2924.87 (64-bit) GPU: ATI 6870 RAM: 32gb CPU: i5-2320 Firefox works perfectly fine, of course with hardware acceleration. In Windows 10, all browsers that aren't based on Chromium work fine. older versions of Chrome work fine with hardware acceleration on. this is my GPU flags from when it works fine forever, with hardware acceleration turned off. With it turned on I'll get maybe 20 minutes before it completely locks up. Enabling crash logs produce nothing because it doesn't 'crash' it leaves nothing in the log because I need to kill the entire lot of Chrome processes when it just freezes. The only thing I captured that *may* have something to do with the browser locking up from dmesg could be this... or could be unrelated, who knows [229866.563896] 4189998 pages RAM [229866.563896] 0 pages HighMem/MovableOnly [229866.563897] 85948 pages reserved [229866.563898] 0 pages cma reserved [229866.563899] 0 pages hwpoisoned [229866.563900] KBD BUG in ../../../../../../../../drivers/2d/lnx/fgl/drm/kernel/gal.c at line: 323! [229866.563912] KBD BUG in ../../../../../../../../drivers/2d/lnx/fgl/drm/kernel/gal.c at line: 304! [229866.563916] KBD BUG in ../../../../../../../../drivers/2d/lnx/fgl/drm/kernel/gal.c at line: 304! [229866.563942] KBD BUG in ../../../../../../../../drivers/2d/lnx/fgl/drm/kernel/gal.c at line: 323! [229866.563952] KBD BUG in ../../../../../../../../drivers/2d/lnx/fgl/drm/kernel/gal.c at line: 323! [229866.563965] KBD BUG in ../../../../../../../../drivers/2d/lnx/fgl/drm/kernel/gal.c at line: 304! [229866.563974] KBD BUG in ../../../../../../../../drivers/2d/lnx/fgl/drm/kernel/gal.c at line: 304! [229866.563989] KBD BUG in ../../../../../../../../drivers/2d/lnx/fgl/drm/kernel/gal.c at line: 323! [229866.563993] KBD BUG in ../../../../../../../../drivers/2d/lnx/fgl/drm/kernel/gal.c at line: 323! [229866.564000] KBD BUG in ../../../../../../../../drivers/2d/lnx/fgl/drm/kernel/gal.c at line: 304! [229866.564004] KBD BUG in ../../../../../../../../drivers/2d/lnx/fgl/drm/kernel/gal.c at line: 304! [229866.595088] KBD BUG in ../../../../../../../../drivers/2d/lnx/fgl/drm/kernel/gal.c at line: 323! [229866.595112] KBD BUG in ../../../../../../../../drivers/2d/lnx/fgl/drm/kernel/gal.c at line: 323! [229866.595195] KBD BUG in ../../../../../../../../drivers/2d/lnx/fgl/drm/kernel/gal.c at line: 304! [229866.595200] KBD BUG in ../../../../../../../../drivers/2d/lnx/fgl/drm/kernel/gal.c at line: 304! [229866.595236] KBD BUG in ../../../../../../../../drivers/2d/lnx/fgl/drm/kernel/gal.c at line: 323! [229866.595249] KBD BUG in ../../../../../../../../drivers/2d/lnx/fgl/drm/kernel Graphics Feature Status Canvas: Software only, hardware acceleration unavailable Flash: Software only, hardware acceleration unavailable Flash Stage3D: Software only, hardware acceleration unavailable Flash Stage3D Baseline profile: Software only, hardware acceleration unavailable Compositing: Software only, hardware acceleration unavailable Multiple Raster Threads: Unavailable Native GpuMemoryBuffers: Software only. Hardware acceleration disabled Rasterization: Software only, hardware acceleration unavailable Video Decode: Software only, hardware acceleration unavailable Video Encode: Software only, hardware acceleration unavailable VPx Video Decode: Software only, hardware acceleration unavailable WebGL: Unavailable WebGL2: Unavailable Driver Bug Workarounds adjust_src_dst_region_for_blitframebuffer clear_uniforms_before_first_program_use disable_framebuffer_cmaa dont_remove_invariant_for_fragment_input force_cube_map_positive_x_allocation init_texture_max_anisotropy regenerate_struct_names scalarize_vec_and_mat_constructor_args Problems Detected GPU process was unable to boot: GPU access is disabled in chrome://settings. Disabled Features: all Accelerated video decode is unavailable on Linux: 137247 Disabled Features: accelerated_video_decode Clear uniforms before first program use on all platforms: 124764, 349137 Applied Workarounds: clear_uniforms_before_first_program_use Linux AMD drivers incorrectly return initial value of 1 for TEXTURE_MAX_ANISOTROPY: 348237 Applied Workarounds: init_texture_max_anisotropy Always rewrite vec/mat constructors to be consistent: 398694 Applied Workarounds: scalarize_vec_and_mat_constructor_args Linux AMD drivers handle struct scopes incorrectly: 403957 Applied Workarounds: regenerate_struct_names Linux ATI drivers crash on binding incomplete cube map texture to FBO: 518889 Applied Workarounds: force_cube_map_positive_x_allocation Limited enabling of Chromium GL_INTEL_framebuffer_CMAA: 535198 Applied Workarounds: disable_framebuffer_cmaa adjust src/dst region if blitting pixels outside read framebuffer on Linux AMD: 664740 Applied Workarounds: adjust_src_dst_region_for_blitframebuffer AMD drivers in Linux require invariant qualifier to match between vertex and fragment shaders: 659326 Applied Workarounds: dont_remove_invariant_for_fragment_input Native GpuMemoryBuffers have been disabled, either via about:flags or command line. Disabled Features: native_gpu_memory_buffers Version Information Data exported 25/02/2017, 00:31:13 Chrome version Chrome/56.0.2924.87 Operating system Linux 3.19.0-32-generic Software rendering list version 12.06 Driver bug list version 9.24 ANGLE commit id a4aaa2de57dc 2D graphics backend Skia/56 bf2d9e02d58ea01f1c239f7e2fc024cba140ccb1 Command Line Args --flag-switches-begin --enable-features=password-import-export --flag-switches-end Driver Information Initialization time 0 In-process GPU true Sandboxed false GPU0 VENDOR = 0x1002, DEVICE= 0x6738 Optimus false AMD switchable false Driver vendor ATI / AMD (Catalyst) Driver version 15.201.1151 Driver date Pixel shader version Vertex shader version Max. MSAA samples Machine model name Machine model version GL_VENDOR ATI Technologies Inc. GL_RENDERER AMD Radeon HD 6800 Series GL_VERSION 4.5.13399 Compatibility Profile Context 15.201.1151 GL_EXTENSIONS Disabled Extensions Window system binding vendor Window system binding version Window system binding extensions Window manager Mutter (Muffin) XDG_CURRENT_DESKTOP X-Cinnamon GDMSESSION cinnamon Compositing manager Yes Direct rendering Yes Reset notification strategy 0x0000 GPU process crash count 0 System visual ID 0 RGBA visual ID 0 Compositor Information Tile Update Mode One-copy Partial Raster Enabled GpuMemoryBuffers Status ATC Software only ATCIA Software only DXT1 Software only DXT5 Software only ETC1 Software only R_8 Software only RG_88 Software only BGR_565 Software only RGBA_4444 Software only RGBX_8888 Software only RGBA_8888 Software only BGRX_8888 Software only BGRA_8888 Software only YVU_420 Software only YUV_420_BIPLANAR Software only UYVY_422 Software only Crashed report ID: Crashes (0) How much crashed? Whole browser Is it a problem with a plugin? No Did this work before? No Chrome version: 56.0.2924.87 Channel: stable OS Version: Arch Flash Version: Shockwave Flash 24.0 r0 it has never worked on 56.x versions, it will freeze/hang about 20 times a day. Nothing appears in crashlogs, I suppose because it isn't 'crashing' and I am forced to kill the tasks to be able to relaunch the browser.
,
Mar 12 2017
I ran the browser with the debug to a txt file and finally had a crash. the line produced was: [14602:15011:0313/010413.614133:ERROR:stunport.cc(89)] Binding request timed out from 0.0.0.x:44703 (any)
,
Mar 14 2017
Tested in chrome reported version # 56.0.2924.87, stable # 57.0.2987.98 and Canary #59.0.3041.0 on Ubuntu 14.04 and not able to reproduce the issue.Please find the screen shot for reference(Attaching current stable screen shot).After re-starting the chrome working as expected not hanging. @quantocks: Could you please create new profile without extensions and apps. Recheck once and provide us with a observations and crash id of the issue which would help us to triage the issue further. Thanks in Advance.
,
Jun 19 2017
It happens with me too, but the whole browser freezes and can't be killed, until I disable my wifi adapter.
,
May 28 2018
Closing issue due to lack of feedback requested but not provided. If the issue still exists please open a new issue with the details requested. |
|||
►
Sign in to add a comment |
|||
Comment 1 by quanto...@gmail.com
, Mar 10 2017