Issue metadata
Sign in to add a comment
|
Rendering problem on MBP under Sierra
Reported by
joe.mur...@jmaconsulting.biz,
Nov 18 2016
|
||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.98 Safari/537.36 Steps to reproduce the problem: 1. Upgrade MacBook Pro to Sierra 2. Use Chrome for a while 3. Contents of tabs eventually stop rendering See various reports on https://productforums.google.com/forum/?utm_medium=email&utm_source=footer#!msg/chrome/pwoOKvS7-cg/hUbBkr3xAAAJ Possible points from various posts: Definitely applies to Early 2011 and Late 2011 macbook pros. One report suggests turning of one of the two graphics processors solves issue. What is the expected behavior? Tabs render content What went wrong? Switching tabs either renders with big black rectangles or sometimes no update and content of previous tab remains visible. Did this work before? Yes Prior to upgrade to Sierra Chrome version: 54.0.2840.98 Channel: stable OS Version: OS X 10.12.1 Flash Version: Shockwave Flash 23.0 r0 Google Community Specialist Beena suggested posting here after 4 weeks and a dozen or so reports of same problems in thread listed above.
,
Nov 18 2016
,
Nov 23 2016
Detailed Steps to reproduce the problem 100% on a MacBook Pro early or late 2011. Those MBP have a discrete and integrated gpu. 1. Upgrade MacBook Pro early or late 2011 to Sierra 2. Start Chrome, open some webpages in tabs 3. Start an application where the MBP switches to the other GPU e.g. a Game, Adobe Illustrator, Photos,... 4. Switch back to Chrome and open new tabs, the tabs will not render anymore or show dummy content from the other tabs 5. Event after closing the application that forced the MBP to switch to the advanced GPU Chrome will stay broken Only solution is to completely close Chrome and restart to fix this.
,
Nov 28 2016
Unable to reproduce the issue on mac os sierra 10.12.1, mid 2012 using chrome reported version #54.0.2840.98 and latest canary #57.0.2934.0. Attached a screen cast for reference. Following are the steps followed to reproduce the issue. ------------ 1. Started Chrome, opened some webpages in tabs. 2. Started an application i.e a Game. 3. Switched back to Chrome and opened new tabs. 4. Observed that the tabs rendered properly without any issues. Reporter@ - Could you please check this issue on latest canary #57.0.2934.0 by creating a new profile without any apps and extensions and please let us know if the issue still persist or not. Thanks...!!
,
Nov 28 2016
I confirm this happening for me as well with a MBP 15" Early 2011 model. Mac OS Sierra 10.12.1 (16B2555) 55.0.2883.59 (Official Build) beta (64-bit) - had the same issue in previous versions, since I upgraded to Sierra (about a month ago). Steps to reproduce issue: 1. Start Chrome, opened some tabs 2. Connect external monitor 3. Open new tabs 4. The new opened tabs had a visual glitch where the page was completely blank or with blacks squares and unresponsive (could not click on anything). The only way to fix this without disabling hardware acceleration is to quit Chrome and open it again.
,
Nov 28 2016
Also confirming this happens on MacBook Pro (15-inch, Late 2011). Also happened on ElCap since June or so. Mac OS Sierra 10.12.1 (16B2555) Chrome 54.0.2840.98 (64-bit) Steps to reproduce: 1. Enable system "Automatic Graphics Switching" in Settings -> Energy Saver 2. Start Chrome, go to chrome://gpu/ 3. All graphics features are enables of hardware accelerated 4. Disable system "Automatic Graphics Switching" in Settings -> Energy Saver 5. Return to chrome://gpu/ 6. Graphics Features are either disabled or software rendering The following errors show in the GPU: - GPU process was unable to boot: Features are disabled upon full but not preliminary GPU info. Disabled Features: all - Intel HD 3000 driver crashes frequently on Mac: 592130 Disabled Features: all Unable to view the bug report due to "You do not have permission to view the requested page." These bugs did not occur in earlier versions of Chrome.
,
Nov 28 2016
@krajshree@chromium.org I made a screen capture of the issue with the Chrome Canary version I downloaded today. https://www.youtube.com/watch?v=mSmsbPl43Ag&feature=youtu.be Issues manifest differently from time to time, sometimes the pageview is all black, all white, shows random white and black areas or shows webpages from other tabs.
,
Nov 29 2016
Also observed on my late 2011 MBP, same specs, same reproduction steps. Running 54.0.2840.98 of Chrome, but also observed on Opera 41.0.2353.56. Firefox is unaffected (and I've had to change to FF to continue working). I can confirm that it was manifesting in OS X El Capitan as well, as I was suffering from it well before my upgrade to Sierra (where it also manifests). Definitely related to GPU usage, and switching between integrated and discrete GPUs while Chrome is open (I have a monitoring app that alerts me to such changes); starting a GPU-intensive app will exacerbate the issue, but even without such apps (running only Chrome and Finder) it is possible to trigger it just through normal browser use.
,
Nov 30 2016
Lopping to Mac and GPU experts who might have some insight about this issue.
,
Nov 30 2016
If you're experiencing this problem, please include the information from about://gpu [after you start experiencing the problem].
,
Nov 30 2016
I was about to say "I can't" because the about://gpu tab renders as black as everything else, but then I realised it's still there, just not visible, and Cmd-A Cmd-C works just fine. Attached the file, that was after the easiest repro: start Chrome on discrete GPU (because of external monitor), unplug monitor to go back to integrated, then open the new tab to observe it as black / corrupted. To be clear: this does not just manifest when using external monitor, it'll come up when using GPU intensive apps on the inbuilt screen only, it's just that using the external monitor is an easy way to make it manifest.
,
Nov 30 2016
,
Dec 1 2016
Sounds similar to issue 661596 .
,
Dec 1 2016
Yeah, both of these are about 2011 machines, marking duplicate. This needs follow-up with Apple.
,
Dec 12 2016
I have a workaround of exiting and restarting Chrome. Is there a way to make Chrome startup so it only uses appropriate GPU via a flag? I will need to be provided link to where to configure startup flags. FWIW, here is the contents of my about://gpu page:
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: Hardware accelerated
Rasterization: Software only, hardware acceleration unavailable
Video Decode: Hardware accelerated
Video Encode: Hardware accelerated
VPx Video Decode: Hardware accelerated
WebGL: Hardware accelerated
Driver Bug Workarounds
disable_framebuffer_cmaa
disable_multimonitor_multisampling
get_frag_data_info_bug
pack_parameters_workaround_with_pack_buffer
regenerate_struct_names
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_shadowed_tex_level_params
Problems Detected
Some GPUs on Mac can perform poorly with GPU rasterization. Disable all known Intel GPUs other than Intel 6th and 7th Generation cards, which have been tested.: 613272, 614468
Disabled Features: gpu_rasterization
Some GPUs on Mac can perform poorly with GPU rasterization. Disable all known AMD GPUs other than the R200, R300, and D series, which have been tested.: 613272, 614468
Disabled Features: gpu_rasterization
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
Mac Drivers store texture level parameters on int16_t that overflow: 610153
Applied Workarounds: use_shadowed_tex_level_params
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
Version Information
Data exported 12/12/2016, 2:20:06 PM
Chrome version Chrome/55.0.2883.87
Operating system Mac OS X 10.12.1
Software rendering list version 11.17
Driver bug list version 9.15
ANGLE commit id 4d208abb1926
2D graphics backend Skia/55 d1740f81c843c65acd58d1b571ce94b90fee99d0
Command Line Args Chrome.app/Contents/MacOS/Google Chrome --flag-switches-begin --flag-switches-end
Driver Information
Initialization time 46
In-process GPU false
Sandboxed true
GPU0 VENDOR = 0x1002, DEVICE= 0x6740 *ACTIVE*
GPU1 VENDOR = 0x8086, DEVICE= 0x0126
Optimus false
AMD switchable true
Driver vendor
Driver version 1.46.22
Driver date
Pixel shader version 4.10
Vertex shader version 4.10
Max. MSAA samples 8
Machine model name MacBookPro
Machine model version 8.2
GL_VENDOR ATI Technologies Inc.
GL_RENDERER AMD Radeon HD 6770M OpenGL Engine
GL_VERSION 4.1 ATI-1.46.22
GL_EXTENSIONS GL_ARB_blend_func_extended GL_ARB_draw_buffers_blend GL_ARB_draw_indirect GL_ARB_ES2_compatibility GL_ARB_explicit_attrib_location GL_ARB_gpu_shader5 GL_ARB_instanced_arrays GL_ARB_internalformat_query GL_ARB_occlusion_query2 GL_ARB_sample_shading GL_ARB_sampler_objects GL_ARB_separate_shader_objects GL_ARB_shader_bit_encoding GL_ARB_shader_subroutine GL_ARB_shading_language_include GL_ARB_tessellation_shader GL_ARB_texture_buffer_object_rgb32 GL_ARB_texture_cube_map_array GL_ARB_texture_gather GL_ARB_texture_query_lod GL_ARB_texture_rgb10_a2ui GL_ARB_texture_storage GL_ARB_texture_swizzle GL_ARB_timer_query GL_ARB_transform_feedback2 GL_ARB_transform_feedback3 GL_ARB_vertex_type_2_10_10_10_rev GL_ARB_viewport_array GL_EXT_debug_label GL_EXT_debug_marker GL_EXT_texture_compression_s3tc GL_EXT_texture_filter_anisotropic GL_EXT_texture_mirror_clamp GL_EXT_texture_sRGB_decode GL_APPLE_client_storage GL_APPLE_container_object_shareable GL_APPLE_flush_render GL_APPLE_object_purgeable GL_APPLE_rgb_422 GL_APPLE_row_bytes GL_APPLE_texture_range GL_ATI_texture_mirror_once GL_NV_texture_barrier
Disabled Extensions
Window system binding vendor
Window system binding version
Window system binding extensions
Direct rendering Yes
Reset notification strategy 0x0000
GPU process crash count 0
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
BGRX_8888 GPU_READ, SCANOUT
BGRA_8888 GPU_READ, SCANOUT, 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
,
Oct 12 2017
I am seeing the same issue in Chrome, and also in electron based apps since upgrading to High Sierra on a MacBook Pro (Retina, 15-inch, Late 2013). Automatic graphics switching is enabled in my Mac Preferences. |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by joe.mur...@jmaconsulting.biz
, Nov 18 2016