Major artifacts and flashing on Chromebook's display, and on connected monitor |
|||||||
Issue descriptionGoogle Chrome 64.0.3282.24 (Official Build) beta (64-bit) Revision 0 Platform 10176.13.1 (Official Build) beta-channel peppy Firmware Version Google_Peppy.4389.117.0 What steps will reproduce the problem? (1) Generic web browsing, switching tabs, profiles (2) (3) What is the expected result? What happens instead? I'm seeing large blocks of black, and screen flashing on the Chromebook's screen, but the attached monitor is fine. Just started after booting new build. Bumped priority because it makes the other display unusable. Attached about:gpu in case it helps. For graphics-related bugs, please copy/paste the contents of the about:gpu page at the end of this report. Note: To properly save this page, select the "Webpage, Complete" option in the Save File dialog. Graphics Feature Status Canvas: Hardware accelerated CheckerImaging: Disabled Flash: Hardware accelerated Flash Stage3D: Hardware accelerated Flash Stage3D Baseline profile: Hardware accelerated Compositing: Hardware accelerated Multiple Raster Threads: Disabled Native GpuMemoryBuffers: Hardware accelerated Rasterization: Hardware accelerated Video Decode: Hardware accelerated WebGL: Hardware accelerated WebGL2: Hardware accelerated Driver Bug Workarounds clear_uniforms_before_first_program_use count_all_in_varyings_packing decode_encode_srgb_for_generatemipmap disable_discard_framebuffer disable_framebuffer_cmaa msaa_is_slow rely_on_implicit_sync_for_swap_buffers scalarize_vec_and_mat_constructor_args Problems Detected Framebuffer discarding causes jumpy scrolling on Mali drivers: 301988 Applied Workarounds: disable_discard_framebuffer Clear uniforms before first program use on all platforms: 124764, 349137 Applied Workarounds: clear_uniforms_before_first_program_use Mesa drivers in ChromeOS handle varyings without static use incorrectly: 333885 Applied Workarounds: count_all_in_varyings_packing Always rewrite vec/mat constructors to be consistent: 398694 Applied Workarounds: scalarize_vec_and_mat_constructor_args On Intel GPUs MSAA performance is not acceptable for GPU rasterization: 527565 Applied Workarounds: msaa_is_slow Use GL_INTEL_framebuffer_CMAA on ChromeOS: 535198 Applied Workarounds: disable_framebuffer_cmaa Disable KHR_blend_equation_advanced until cc shaders are updated: 661715 Applied Workarounds: disable(GL_KHR_blend_equation_advanced), disable(GL_KHR_blend_equation_advanced_coherent) Decode and Encode before generateMipmap for srgb format textures on Chromeos Intel: 634519 Applied Workarounds: decode_encode_srgb_for_generatemipmap Avoid waiting on a egl fence before pageflipping and rely on implicit sync.: 721463 Applied Workarounds: rely_on_implicit_sync_for_swap_buffers Raster is using a single thread. Disabled Features: multiple_raster_threads Checker-imaging has been disabled via finch trial or the command line. Disabled Features: checker_imaging Version Information Data exported 12/14/2017, 7:49:22 PM Chrome version Chrome/64.0.3282.24 Operating system Linux 3.8.11 Software rendering list URL https://chromium.googlesource.com/chromium/src/+/0/gpu/config/software_rendering_list.json Driver bug list URL https://chromium.googlesource.com/chromium/src/+/0/gpu/config/gpu_driver_bug_list.json ANGLE commit id c13c3dde6d24 2D graphics backend Skia/64 0 Command Line /opt/google/chrome/chrome --ppapi-flash-path=/opt/google/chrome/pepper/libpepflashplayer.so --ppapi-flash-version=28.0.0.129 --ui-prioritize-in-gpu-process --use-gl=egl --enable-native-gpu-memory-buffers --gpu-sandbox-failures-fatal=yes --enable-logging --log-level=1 --use-cras --enable-wayland-server --user-data-dir=/home/chronos --max-unused-resource-memory-usage-percentage=5 --login-profile=user --has-chromeos-keyboard --default-wallpaper-large=/usr/share/chromeos-assets/wallpaper/oem_large.jpg --default-wallpaper-small=/usr/share/chromeos-assets/wallpaper/oem_small.jpg --default-wallpaper-is-oem --guest-wallpaper-large=/usr/share/chromeos-assets/wallpaper/guest_large.jpg --guest-wallpaper-small=/usr/share/chromeos-assets/wallpaper/guest_small.jpg --enable-consumer-kiosk --enterprise-enrollment-initial-modulus=15 --enterprise-enrollment-modulus-limit=19 --login-manager --first-exec-after-boot --vmodule=tablet_power_button_controller=1,*chromeos/login/*=1,auto_enrollment_controller=1,*plugin*=2,*zygote*=1,*/ui/ozone/*=1,*/ui/display/manager/chromeos/*=1,*night_light*=1,power_button_observer=2,webui_login_view=2,lock_state_controller=2,webui_screen_locker=2,screen_locker=2 Driver Information Initialization time 235 In-process GPU false Passthrough Command Decoder false Supports overlays false Sandboxed true GPU0 VENDOR = 0x8086, DEVICE= 0x0a06 Optimus false Optimus false AMD switchable false Driver vendor Mesa Driver version 17.2.0 Driver date Pixel shader version 3.00 Vertex shader version 3.00 Max. MSAA samples 8 Machine model name Machine model version GL_VENDOR Intel Open Source Technology Center GL_RENDERER Mesa DRI Intel(R) Haswell Mobile GL_VERSION OpenGL ES 3.0 Mesa 17.3.0-devel (git-11adea4b24) GL_EXTENSIONS GL_EXT_blend_minmax GL_EXT_multi_draw_arrays GL_EXT_texture_filter_anisotropic GL_EXT_texture_compression_dxt1 GL_EXT_texture_format_BGRA8888 GL_OES_compressed_ETC1_RGB8_texture GL_OES_depth24 GL_OES_element_index_uint GL_OES_fbo_render_mipmap GL_OES_mapbuffer GL_OES_rgb8_rgba8 GL_OES_standard_derivatives GL_OES_stencil8 GL_OES_texture_3D GL_OES_texture_float GL_OES_texture_float_linear GL_OES_texture_half_float GL_OES_texture_half_float_linear GL_OES_texture_npot GL_OES_vertex_half_float GL_EXT_texture_sRGB_decode GL_OES_EGL_image GL_OES_depth_texture GL_OES_packed_depth_stencil GL_EXT_texture_type_2_10_10_10_REV GL_OES_get_program_binary GL_APPLE_texture_max_level GL_EXT_discard_framebuffer GL_EXT_read_format_bgra GL_EXT_frag_depth GL_NV_fbo_color_attachments GL_OES_EGL_image_external GL_OES_EGL_sync GL_OES_vertex_array_object GL_ANGLE_texture_compression_dxt3 GL_ANGLE_texture_compression_dxt5 GL_EXT_robustness GL_EXT_texture_rg GL_EXT_unpack_subimage GL_NV_draw_buffers GL_NV_read_buffer GL_NV_read_depth GL_NV_read_depth_stencil GL_NV_read_stencil GL_EXT_draw_buffers GL_EXT_map_buffer_range GL_KHR_debug GL_KHR_robustness GL_OES_depth_texture_cube_map GL_OES_required_internalformat GL_OES_surfaceless_context GL_EXT_color_buffer_float GL_EXT_separate_shader_objects GL_EXT_shader_integer_mix GL_INTEL_performance_query GL_EXT_compressed_ETC1_RGB8_sub_texture GL_EXT_draw_buffers_indexed GL_EXT_draw_elements_base_vertex GL_EXT_polygon_offset_clamp GL_EXT_texture_border_clamp GL_KHR_blend_equation_advanced GL_KHR_context_flush_control GL_KHR_robust_buffer_access_behavior GL_OES_draw_buffers_indexed GL_OES_draw_elements_base_vertex GL_OES_sample_shading GL_OES_sample_variables GL_OES_shader_multisample_interpolation GL_OES_texture_border_clamp GL_OES_texture_stencil8 GL_EXT_blend_func_extended GL_KHR_no_error GL_EXT_clip_cull_distance GL_MESA_shader_integer_functions Disabled Extensions GL_KHR_blend_equation_advanced GL_KHR_blend_equation_advanced_coherent Window system binding vendor Mesa Project Window system binding version 1.4 (DRI2) Window system binding extensions EGL_EXT_image_dma_buf_import EGL_EXT_image_dma_buf_import_modifiers EGL_KHR_config_attribs EGL_KHR_create_context EGL_KHR_create_context_no_error EGL_KHR_fence_sync EGL_KHR_get_all_proc_addresses EGL_KHR_gl_renderbuffer_image EGL_KHR_gl_texture_2D_image EGL_KHR_gl_texture_3D_image EGL_KHR_gl_texture_cubemap_image EGL_KHR_image_base EGL_KHR_no_config_context EGL_KHR_reusable_sync EGL_KHR_surfaceless_context EGL_KHR_wait_sync EGL_MESA_configless_context EGL_MESA_drm_image EGL_MESA_image_dma_buf_export Direct rendering Yes Reset notification strategy 0x8261 GPU process crash count 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 GPU_READ_CPU_READ_WRITE, GPU_READ_CPU_READ_WRITE_PERSISTENT R_16 Software only RG_88 GPU_READ_CPU_READ_WRITE, GPU_READ_CPU_READ_WRITE_PERSISTENT BGR_565 GPU_READ RGBA_4444 Software only RGBX_8888 GPU_READ, SCANOUT, SCANOUT_CPU_READ_WRITE RGBA_8888 GPU_READ, SCANOUT_CPU_READ_WRITE BGRX_8888 GPU_READ, SCANOUT, SCANOUT_CPU_READ_WRITE BGRX_1010102 Software only BGRA_8888 GPU_READ, SCANOUT_CPU_READ_WRITE, GPU_READ_CPU_READ_WRITE, GPU_READ_CPU_READ_WRITE_PERSISTENT RGBA_F16 Software only YVU_420 GPU_READ YUV_420_BIPLANAR SCANOUT_CAMERA_READ_WRITE UYVY_422 Software only Display(s) Information Info Display[3850489720471552] bounds=0,0 1366x768, workarea=0,0 1366x768, scale=1, internal Color space information {primaries:BT709, transfer:IEC61966_2_1, matrix:RGB, range:FULL} Bits per color component 8 Bits per pixel 24 Info Display[4693687208595457] bounds=-106,-900 1600x900, workarea=-106,-900 1600x900, scale=1, external Color space information {primaries:BT709, transfer:IEC61966_2_1, matrix:RGB, range:FULL} Bits per color component 8 Bits per pixel 24 Video Acceleration Information Decode h264 baseline up to 4096x4096 pixels Decode h264 main up to 4096x4096 pixels Decode h264 high up to 4096x4096 pixels Decode vp9 profile0 up to 4096x4096 pixels Log Messages [1237:1265:1214/173324.707737:VERBOSE1:drm_device_manager.cc(53)] : Could not initialize DRM device for /sys/devices/platform/vgem/drm/card1 [1237:1265:1214/173325.764412:VERBOSE1:drm_display.cc(105)] : DRM configuring: device=/sys/devices/pci0000:00/0000:00:02.0/drm/card0 crtc=19 connector=28 origin=0,0 size=1366x768 [1237:1265:1214/173325.780756:VERBOSE1:drm_display.cc(105)] : DRM configuring: device=/sys/devices/pci0000:00/0000:00:02.0/drm/card0 crtc=22 connector=38 origin=0,828 size=1600x900 [1237:1265:1214/175344.375503:WARNING:screen_manager.cc(114)] : Display controller (crtc=19) already present. [1237:1265:1214/175344.378679:WARNING:screen_manager.cc(114)] : Display controller (crtc=22) already present. [1237:1265:1214/175344.388735:VERBOSE1:drm_display.cc(105)] : DRM configuring: device=/sys/devices/pci0000:00/0000:00:02.0/drm/card0 crtc=19 connector=28 origin=0,0 size=0x0 [1237:1265:1214/175345.476652:VERBOSE1:drm_display.cc(105)] : DRM configuring: device=/sys/devices/pci0000:00/0000:00:02.0/drm/card0 crtc=22 connector=38 origin=0,0 size=0x0 [1237:1265:1214/175421.975263:WARNING:screen_manager.cc(114)] : Display controller (crtc=19) already present. [1237:1265:1214/175421.975393:WARNING:screen_manager.cc(114)] : Display controller (crtc=22) already present. [1237:1265:1214/175421.977024:VERBOSE1:drm_display.cc(105)] : DRM configuring: device=/sys/devices/pci0000:00/0000:00:02.0/drm/card0 crtc=19 connector=28 origin=0,0 size=1366x768 [1237:1265:1214/175422.896659:VERBOSE1:drm_display.cc(105)] : DRM configuring: device=/sys/devices/pci0000:00/0000:00:02.0/drm/card0 crtc=22 connector=38 origin=0,828 size=1600x900 [1237:1265:1214/182407.572135:WARNING:screen_manager.cc(114)] : Display controller (crtc=19) already present. [1237:1265:1214/182407.575616:WARNING:screen_manager.cc(114)] : Display controller (crtc=22) already present. [1237:1265:1214/182407.580678:VERBOSE1:drm_display.cc(105)] : DRM configuring: device=/sys/devices/pci0000:00/0000:00:02.0/drm/card0 crtc=19 connector=28 origin=0,0 size=0x0 [1237:1265:1214/182408.677525:VERBOSE1:drm_display.cc(105)] : DRM configuring: device=/sys/devices/pci0000:00/0000:00:02.0/drm/card0 crtc=22 connector=38 origin=0,0 size=0x0 [1237:1265:1214/183256.645363:WARNING:screen_manager.cc(114)] : Display controller (crtc=19) already present. [1237:1265:1214/183256.645479:WARNING:screen_manager.cc(114)] : Display controller (crtc=22) already present. [1237:1265:1214/183256.680053:VERBOSE1:drm_display.cc(105)] : DRM configuring: device=/sys/devices/pci0000:00/0000:00:02.0/drm/card0 crtc=19 connector=28 origin=0,0 size=1366x768 [1237:1265:1214/183257.604132:VERBOSE1:drm_display.cc(105)] : DRM configuring: device=/sys/devices/pci0000:00/0000:00:02.0/drm/card0 crtc=22 connector=38 origin=0,828 size=1600x900 [1237:1237:1214/184407.202840:WARNING:ipc_message_attachment_set.cc(49)] : MessageAttachmentSet destroyed with unconsumed attachments: 0/1 [1237:1237:1214/184407.202929:WARNING:ipc_message_attachment_set.cc(49)] : MessageAttachmentSet destroyed with unconsumed attachments: 0/1
,
Dec 17 2017
,
Dec 18 2017
probably same as http://crbug.com/781060
,
Dec 18 2017
http://crbug.com/781060 should be fixed and should only affect to v3.8 kernel devices. As cave is v3.18, I suspect it is different from crbug/781060 and probably related to mesa uprev in 10173.0.0. Flashed to 10176.13.1 on my own cave and can not reproduce the issue. Ran some tests and all passed. @krb do you have more specifics on how to reproduce this issue?
,
Dec 18 2017
Just realize the original post krb posted is on peppy, which is on kernel v3.8. Will do the tests again to see if the problem is the same as 781060.
,
Dec 18 2017
Same, Flashed peppy to the questioned version and did some tests. None of them could reproduce the glitch. Would mark this as WontFix until there's more details.
,
Dec 18 2017
What other details would help? btw, I'm seeing this even without a monitor plugged in.
,
Dec 18 2017
It might be complicate, but if you could find a specific website/chrome test/chromeos test/a sequence of steps that consistently generates the flashing, that would definitely help and I will be appreciate. I do use it for browsing website for 10 minutes and the website of mine is works as expected (no flashing or corrupt graphics).
,
Dec 19 2017
Do you have any special settings in your chromebook?
,
Dec 19 2017
I don't think I have any flags overridden. I have the usual (mandatory?) corp extensions. I can temporarily clear it by cycling the monitor. Once the problem starts, it just gets worse. I seem to be able to aggravate it by going to the top of a webpage then immediately to the bottom - ^home, ^end.
,
Dec 19 2017
I tried to hit ^home/^end multiple times at google search page but in vain. Could you confirm that 10176.13.1 is the first time you observe the problem?
,
Dec 19 2017
I wrote the bug a few hours after whatever update occurred that day. I use this Chromebook daily, and try to write bugs like this as soon as they occur in case it helps someone revert a change. (I assumed that I was on the dev-channel.) So if there hasn't been an update since 10176.13.1 (what it says I have now), then that's what triggered it.
,
Dec 19 2017
I have the glitches permanently on cave, no way to get rid of them. I'm not a tester so can't afford clearing up the device but my usage pattern is the following: 1. Attach UDL3 display 2. Close the lid 3. Launch some android apps, launch crosh xiwi window, etc. 4. Enter Expose' mode, see flashing and other artifacts flying around 5. It does not matter if you close all the windows except for chrome - the problem persists
,
Dec 19 2017
,
Dec 19 2017
,
Dec 19 2017
Assigning to tutankhamen@ to see if it is something UDL related.
,
Dec 28 2017
I have the same problem on my LG Chromebase which I use every day for 8h at least. Problem occured a week ago right after the last update to the following version: Version 64.0.3282.41 (Official Build) beta (64-bit) Problem exists permanently since update and it flooding my screen with black rectangles in any applications but most notably in those cases: 1) Many windows overlap each other and top window is closed after. In this case window which should be on top unable to redraw areas which are previously hidden by closed window. 2) Some times when many windows open and I try to drag something or scroll tab with mouse black rectangles flicking in any random part of the screen (not only in the tab which have focus but in other windows and over shelf panel). My platform details: Platform 10176.22.0 (Official Build) beta-channel monroe Firmware Google_Monroe.4921.17.0 Channel Currently on beta Blink 537.36 (@) V8 6.4.388.9 User Agent Mozilla/5.0 (X11; CrOS x86_64 10176.22.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.41 Safari/537.36 Command Line /opt/google/chrome/chrome --ppapi-flash-path=/opt/google/chrome/pepper/libpepflashplayer.so --ppapi-flash-version=28.0.0.133 --ui-prioritize-in-gpu-process --use-gl=egl --enable-native-gpu-memory-buffers --gpu-sandbox-failures-fatal=yes --enable-logging --log-level=1 --use-cras --enable-wayland-server --user-data-dir=/home/chronos --max-unused-resource-memory-usage-percentage=5 --login-profile=user --aura-legacy-power-button --touchscreen-usable-while-screen-off --default-wallpaper-large=/usr/share/chromeos-assets/wallpaper/default_large.jpg --default-wallpaper-small=/usr/share/chromeos-assets/wallpaper/default_small.jpg --child-wallpaper-large=/usr/share/chromeos-assets/wallpaper/child_large.jpg --child-wallpaper-small=/usr/share/chromeos-assets/wallpaper/child_small.jpg --guest-wallpaper-large=/usr/share/chromeos-assets/wallpaper/guest_large.jpg --guest-wallpaper-small=/usr/share/chromeos-assets/wallpaper/guest_small.jpg --enable-consumer-kiosk --enterprise-enrollment-initial-modulus=15 --enterprise-enrollment-modulus-limit=19 --login-manager --first-exec-after-boot --vmodule=tablet_power_button_controller=1,*chromeos/login/*=1,auto_enrollment_controller=1,*plugin*=2,*zygote*=1,*/ui/ozone/*=1,*/ui/display/manager/chromeos/*=1,*night_light*=1,power_button_observer=2,webui_login_view=2,lock_state_controller=2,webui_screen_locker=2,screen_locker=2 Build Date Wednesday, December 20, 2017
,
Dec 28 2017
I'm still seeing on .41 as well. Rebooting seems to help for a little while, but it gets worse until the screen eventually stops updating. Once, the trigger page seemed to be Maps possibly, but it didn't occur the first time that I opened Maps.
,
Jan 4 2018
Ok, I believe I at least have a consistent way to duplicate it. I was able to run without issue for an entire day, but the instant I loaded youtube.com on the second profile/user the next day, I saw artifacts, even on the primary profile/user.
,
Jan 8 2018
Flooding of black rectangles on my screen made my Chromebase totally worthless for work. However I discovered some common things while it happens: 1) In most cases black rects appearing after any animation start on the page (for example GIF animation). 2) After first black rect appear then screen start flooded with black rects massively especially in areas of moving mouse pointer and/or windows overlaping each other.
,
Jan 8 2018
I recorded a video when Chrome OS GUI started crashing. Sorry for quality because performance of recording video process started degrading in advance of overall disaster before the end of the video. In reality GUI was responsive like good 60 fps application and music was playing all the time from start to finish. However all artifacts on screen which were recorded on the video were real and clearly seen by me also (it is not a recording video software bug). https://youtu.be/nuVTgtXIDs0
,
Jan 8 2018
YouTube was required me to remove copyrighted sound from the video (see comment above) which was published in unlisted mode. To protect my video from deletion I disabled audio track. If you want to see the whole picture just send me email or increase file attachments limit to 25 MB (video size is 18 MB).
,
Jan 9 2018
Just received update for my Chromebase. Chrome OS was passed some heavy load tests after that without any black rects. For now I'll try working with it for a week to proof its stability.
,
Jan 9 2018
I have pushed a fix into beta channel in 10176. Please keep update if you see the same issue again.
,
Jan 10 2018
I saw this problem every day until today. I can't duplicate it with the new build. I would call it fixed.
,
Jan 10 2018
I just wanted to confirm that after one full day of use, I have not experienced any artifacts after the update, whereas I would see them constantly before.
,
Jan 12 2018
|
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by k...@chromium.org
, Dec 16 2017