Issue metadata
Sign in to add a comment
|
Missing tiles with external monitor connected to Macbook Pro |
||||||||||||||||||||||||
Issue descriptionChrome Version: 58.0.3029.81 (64-bit) OS: 10.12.4 What steps will reproduce the problem? (1) open gmail.com (2) drag window to ~full screen (3) scroll (not always needed) What is the expected result? Gmail is displayed correctly. On my previous MBP (mid-2013), this worked fine. On my new 2016 MBP, I encounter display glitches. What happens instead? Gray boxes appear over top of Gmail, and controls randomly flicker and vanish. The about:gpu report indicates some bad things are happening. 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 unavailable 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 decode_encode_srgb_for_generatemipmap disable_framebuffer_cmaa disable_multimonitor_multisampling get_frag_data_info_bug pack_parameters_workaround_with_pack_buffer regenerate_struct_names remove_invariant_and_centroid_for_essl3 reset_base_mipmap_level_before_texstorage scalarize_vec_and_mat_constructor_args set_zero_level_before_generating_mipmap unfold_short_circuit_as_ternary_operation unpack_alignment_workaround_with_unpack_buffer use_intermediary_for_copy_texture_image use_unused_standard_shared_blocks Problems Detected GPU process was unable to boot: GPU access is disabled in chrome://settings. Disabled Features: all Multisampling is buggy on OSX when multiple monitors are connected: 237931 Applied Workarounds: disable_multimonitor_multisampling Unfold short circuit on Mac OS X: 307751 Applied Workarounds: unfold_short_circuit_as_ternary_operation Always rewrite vec/mat constructors to be consistent: 398694 Applied Workarounds: scalarize_vec_and_mat_constructor_args Mac drivers handle struct scopes incorrectly: 403957 Applied Workarounds: regenerate_struct_names glGenerateMipmap fails if the zero texture level is not set on some Mac drivers: 560499 Applied Workarounds: set_zero_level_before_generating_mipmap Pack parameters work incorrectly with pack buffer bound: 563714 Applied Workarounds: pack_parameters_workaround_with_pack_buffer Alignment works incorrectly with unpack buffer bound: 563714 Applied Workarounds: unpack_alignment_workaround_with_unpack_buffer copyTexImage2D fails when reading from IOSurface on multiple GPU types.: 581777 Applied Workarounds: use_intermediary_for_copy_texture_image Limited enabling of Chromium GL_INTEL_framebuffer_CMAA: 535198 Applied Workarounds: disable_framebuffer_cmaa glGetFragData{Location|Index} works incorrectly on Max: 638340 Applied Workarounds: get_frag_data_info_bug glTexStorage* are buggy when base mipmap level is not 0: 640506 Applied Workarounds: reset_base_mipmap_level_before_texstorage Decode and encode before generateMipmap for srgb format textures on macosx: 634519 Applied Workarounds: decode_encode_srgb_for_generatemipmap Insert statements to reference all members in unused std140/shared blocks on Mac: 618464 Applied Workarounds: use_unused_standard_shared_blocks adjust src/dst region if blitting pixels outside read framebuffer on Mac: 644740 Applied Workarounds: adjust_src_dst_region_for_blitframebuffer Mac driver GL 4.1 requires invariant and centroid to match between shaders: 639760, 641129 Applied Workarounds: remove_invariant_and_centroid_for_essl3 Disable KHR_blend_equation_advanced until cc shaders are updated: 661715 Version Information Data exported 4/25/2017, 3:30:36 PM Chrome version Chrome/58.0.3029.81 Operating system Mac OS X 10.12.4 Software rendering list version 12.20 Driver bug list version 9.36 ANGLE commit id 461d9a3060e3 2D graphics backend Skia/58 4c81ba6ba3a3270db809bf7d4c3bc782694a56a4 Command Line Args Chrome.app/Contents/MacOS/Google Chrome --flag-switches-begin --flag-switches-end Driver Information Initialization time 175 In-process GPU false Passthrough Command Decoder false Sandboxed true GPU0 VENDOR = 0x1002, DEVICE= 0x67ef *ACTIVE* GPU1 VENDOR = 0x8086, DEVICE= 0x191b Optimus false Optimus false AMD switchable true Driver vendor Driver version Driver date Pixel shader version Vertex shader version Max. MSAA samples Machine model name MacBookPro Machine model version 13.3 GL_VENDOR GL_RENDERER GL_VERSION GL_EXTENSIONS Disabled Extensions GL_KHR_blend_equation_advanced GL_KHR_blend_equation_advanced_coherent Window system binding vendor Window system binding version Window system binding extensions Direct rendering Yes Reset notification strategy 0x0000 GPU process crash count 3 Compositor Information Tile Update Mode Zero-copy Partial Raster Enabled GpuMemoryBuffers Status ATC Software only ATCIA Software only DXT1 Software only DXT5 Software only ETC1 Software only R_8 GPU_READ_CPU_READ_WRITE, GPU_READ_CPU_READ_WRITE_PERSISTENT RG_88 Software only BGR_565 Software only RGBA_4444 Software only RGBX_8888 Software only RGBA_8888 GPU_READ, SCANOUT, SCANOUT_CPU_READ_WRITE BGRX_8888 GPU_READ, SCANOUT, SCANOUT_CPU_READ_WRITE BGRA_8888 GPU_READ, SCANOUT, SCANOUT_CPU_READ_WRITE, GPU_READ_CPU_READ_WRITE, GPU_READ_CPU_READ_WRITE_PERSISTENT YVU_420 Software only YUV_420_BIPLANAR GPU_READ_CPU_READ_WRITE, GPU_READ_CPU_READ_WRITE_PERSISTENT UYVY_422 GPU_READ_CPU_READ_WRITE, GPU_READ_CPU_READ_WRITE_PERSISTENT Log Messages [10028:16443:0424/231045.205540:ERROR:gpu_watchdog_thread.cc(373)] : The GPU process hung. Terminating after 10000 ms. GpuProcessHostUIShim: The GPU process crashed! [11106:15931:0424/233037.337643:ERROR:gpu_watchdog_thread.cc(373)] : The GPU process hung. Terminating after 10000 ms. GpuProcessHostUIShim: The GPU process crashed! [11786:16443:0424/234810.573617:ERROR:gpu_watchdog_thread.cc(373)] : The GPU process hung. Terminating after 10000 ms. GpuProcessHostUIShim: The GPU process crashed!
,
Apr 28 2017
,
Apr 28 2017
Not sure this is a dup, since this bug occurs on Mac as opposed to Windows. Is this a cross-platform issue?
,
Apr 28 2017
Oops I edited the wrong bug, sorry about the confusion. This looks like GPU process has hung and not recovered, possibly during resizing?
,
Apr 28 2017
,
Apr 28 2017
Yes, looks like the GPU process is hanging frequently, and when that happens (and I assume software fallback occurs), I start to see the aforementioned problems. When you say resizing, do you mean window resizing?
,
Apr 28 2017
Also, in working with techstop on this, once the GPU process crashes, the problem can be reproduced on the internal display.
,
Apr 28 2017
If you just disable hardware accel do the problems reproduce? That'd be easier to debug.
,
Apr 28 2017
The problems still occur if I disable HW accel in Chrome prefs.
,
Apr 28 2017
It almost seems like the problem is in the SW mode, since I don't see the problem when HW accel is active.
,
Apr 28 2017
Right, so if you disable hardware accel, what's the minimum set of things you need to repro. Do you need an external monitor?
,
Apr 28 2017
I just reproduced it via the following steps: 0) Disable HW accel in Chrome Canary prefs 1) Attach external monitor 2) Relaunch Chrome Canary and make full width/height 3) Open gmail.com 4) See problem I can intermittently reproduce it with the same steps, minus the external display. Usually I have to perform some other step that seems to tax the renderer - one common one is to view a lengthy PDF in Chrome, where I commonly see missing 512x512 (approximately) blocks. Sometimes they eventually fill in, sometimes they don't.
,
May 1 2017
,
May 1 2017
,
May 1 2017
,
May 4 2017
Any idea why the GPU process is crashing? |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by juberti@chromium.org
, Apr 25 2017