New issue
Advanced search Search tips

Issue 808391 link

Starred by 3 users

Issue metadata

Status: Fixed
Owner: ----
Closed: Feb 2018
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

On Bob, aka Asus C101PA, the screen flashes when a video is played while being scaled by half

Reported by a0795a...@gmail.com, Feb 2 2018

Issue description

UserAgent: Mozilla/5.0 (X11; CrOS aarch64 10176.65.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.134 Safari/537.36
Platform: 10176.65.0 (Official Build) beta-channel bob

Example URL:
https://www.youtube.com/watch?v=Fa1bj14j4_8

Steps to reproduce the problem:
1. Open a youtube video, preferably with >=1440p quality
2. Set video quality double of viewport
e.g. 1440p video on 720p viewport, 720p video on 360p viewport etc. This info is available in "Stats for Nerds"
3. Wait until the UI overlay (play button, progress bar, etc) disappears. Make sure there are no overlays, windows, cursor on top of the video viewport.
Some channels have small icon overlayed on each of their video, on the bottom right side. You need to find a video without one to reproduce.

What is the expected behavior?
The video plays smoothly

What went wrong?
Lower half of the screen goes black, and the rest flashes rapidly.
This video shows shows what it looks like: https://www.youtube.com/watch?v=DsZXZLKH8F4

Did this work before? No 

Is it a problem with Flash or HTML5? N/A

Does this work in other browsers? N/A

Chrome version: 64.0.3282.134  Channel: beta
OS Version: 10176.65.0
Flash Version: 28.0.0.137

Contents of chrome://gpu: 
Note: To properly save this page, select the "Webpage, Complete" option in the Save File dialog.
Graphics Feature Status
Canvas: Hardware accelerated
CheckerImaging: Enabled
Flash: Hardware accelerated
Flash Stage3D: Hardware accelerated
Flash Stage3D Baseline profile: Hardware accelerated
Compositing: Hardware accelerated
Multiple Raster Threads: Disabled
Native GpuMemoryBuffers: Software only. Hardware acceleration disabled
Rasterization: Software only, hardware acceleration unavailable
Video Decode: Software only. Hardware acceleration disabled
WebGL: Hardware accelerated
WebGL2: Hardware accelerated
Driver Bug Workarounds
clear_uniforms_before_first_program_use
disable_discard_framebuffer
disable_framebuffer_cmaa
disable_non_empty_post_sub_buffers_for_onscreen_surfaces
disable_program_caching_for_transform_feedback
scalarize_vec_and_mat_constructor_args
use_virtualized_gl_contexts
Problems Detected
GPU rasterization on CrOS is blacklisted on non-Intel GPUs for now.: 684094
Disabled Features: gpu_rasterization
The Mali-Txxx driver does not guarantee flush ordering: 154715, 10068, 269829, 294779, 285292
Applied Workarounds: use_virtualized_gl_contexts
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
Always rewrite vec/mat constructors to be consistent: 398694
Applied Workarounds: scalarize_vec_and_mat_constructor_args
The Mali-Txxx driver hangs when reading from currently displayed buffer: 457511
Applied Workarounds: disable_non_empty_post_sub_buffers_for_onscreen_surfaces
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)
Program binaries don't contain transform feedback varyings on Mali GPUs: 778871
Applied Workarounds: disable_program_caching_for_transform_feedback
Accelerated video decode has been disabled, either via blacklist, about:flags or the command line.
Disabled Features: video_decode
Raster is using a single thread.
Disabled Features: multiple_raster_threads
Native GpuMemoryBuffers have been disabled, either via about:flags or command line.
Disabled Features: native_gpu_memory_buffers
Version Information
Data exported	2018. 2. 2. 오후 7:53:30
Chrome version	Chrome/64.0.3282.134
Operating system	Linux 4.4.96-12272-g2cbee1af2bec-dirty
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	2987f0fde973
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.137 --ui-prioritize-in-gpu-process --use-gl=egl --enable-drm-atomic --enable-hardware-overlays=single-fullscreen,single-on-top --enable-webgl-image-chromium --enable-features=Pepper3DImageChromium --num-raster-threads=1 --gpu-sandbox-failures-fatal=yes --gpu-sandbox-start-early --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 --enable-touchview --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 --arc-availability=officially-supported --enterprise-enrollment-initial-modulus=15 --enterprise-enrollment-modulus-limit=19 --login-user=a0795a089@gmail.com --login-profile=a0d816ec16d1f1db28c5f7fe5f3f0a32147d1a13 --flag-switches-begin --disable-accelerated-video-decode --flag-switches-end --vmodule=*arc/*=1,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 --enable-features=Pepper3DImageChromium
Driver Information
Initialization time	39
In-process GPU	false
Passthrough Command Decoder	false
Supports overlays	false
Sandboxed	true
GPU0	VENDOR = 0x0000, DEVICE= 0x0000
Optimus	false
Optimus	false
AMD switchable	false
Driver vendor	ES
Driver version	3.1
Driver date	
Pixel shader version	3.10
Vertex shader version	3.10
Max. MSAA samples	16
Machine model name	
Machine model version	
GL_VENDOR	ARM
GL_RENDERER	Mali-T860
GL_VERSION	OpenGL ES 3.1 v1.r12p0-04rel0.e86a0cd29e61af8c0d7f229d28757db6
GL_EXTENSIONS	GL_ARM_rgba8 GL_ARM_mali_shader_binary GL_OES_depth24 GL_OES_depth_texture GL_OES_depth_texture_cube_map GL_OES_packed_depth_stencil GL_OES_rgb8_rgba8 GL_EXT_read_format_bgra GL_OES_compressed_paletted_texture GL_OES_compressed_ETC1_RGB8_texture GL_OES_standard_derivatives GL_OES_EGL_image GL_OES_EGL_image_external GL_OES_EGL_image_external_essl3 GL_OES_EGL_sync GL_OES_texture_npot GL_OES_vertex_half_float GL_OES_required_internalformat GL_OES_vertex_array_object GL_OES_mapbuffer GL_EXT_texture_format_BGRA8888 GL_EXT_texture_rg GL_EXT_texture_type_2_10_10_10_REV GL_OES_fbo_render_mipmap GL_OES_element_index_uint GL_EXT_shadow_samplers GL_OES_texture_compression_astc GL_KHR_texture_compression_astc_ldr GL_KHR_texture_compression_astc_hdr GL_KHR_texture_compression_astc_sliced_3d GL_KHR_debug GL_EXT_occlusion_query_boolean GL_EXT_disjoint_timer_query GL_EXT_blend_minmax GL_EXT_discard_framebuffer GL_OES_get_program_binary GL_OES_texture_3D GL_EXT_texture_storage GL_EXT_multisampled_render_to_texture GL_OES_surfaceless_context GL_OES_texture_stencil8 GL_EXT_shader_pixel_local_storage GL_ARM_shader_framebuffer_fetch GL_ARM_shader_framebuffer_fetch_depth_stencil GL_ARM_mali_program_binary GL_EXT_sRGB GL_EXT_sRGB_write_control GL_EXT_texture_sRGB_decode GL_KHR_blend_equation_advanced GL_KHR_blend_equation_advanced_coherent GL_OES_texture_storage_multisample_2d_array GL_OES_shader_image_atomic GL_EXT_robustness GL_EXT_draw_buffers_indexed GL_OES_draw_buffers_indexed GL_EXT_texture_border_clamp GL_OES_texture_border_clamp GL_EXT_texture_cube_map_array GL_OES_texture_cube_map_array GL_OES_sample_variables GL_OES_sample_shading GL_OES_shader_multisample_interpolation GL_EXT_shader_io_blocks GL_OES_shader_io_blocks GL_EXT_tessellation_shader GL_OES_tessellation_shader GL_EXT_primitive_bounding_box GL_OES_primitive_bounding_box GL_EXT_geometry_shader GL_OES_geometry_shader GL_ANDROID_extension_pack_es31a GL_EXT_gpu_shader5 GL_OES_gpu_shader5 GL_EXT_texture_buffer GL_OES_texture_buffer GL_EXT_copy_image GL_OES_copy_image GL_EXT_color_buffer_half_float GL_EXT_color_buffer_float GL_OVR_multiview GL_OVR_multiview2 GL_OVR_multiview_multisampled_render_to_texture
Disabled Extensions	GL_KHR_blend_equation_advanced GL_KHR_blend_equation_advanced_coherent
Window system binding vendor	ARM
Window system binding version	1.4 Midgard-"r12p0-04rel0"
Window system binding extensions	EGL_KHR_partial_update EGL_EXT_swap_buffers_with_damage EGL_KHR_swap_buffers_with_damage EGL_EXT_image_dma_buf_import EGL_EXT_image_dma_buf_import_modifiers EGL_KHR_image_pixmap EGL_EXT_image_flush_external EGL_ANDROID_native_fence_sync EGL_KHR_config_attribs EGL_KHR_image EGL_KHR_image_base EGL_KHR_fence_sync EGL_KHR_wait_sync EGL_KHR_gl_colorspace EGL_KHR_get_all_proc_addresses EGL_IMG_context_priority EGL_ARM_pixmap_multisample_discard EGL_ARM_implicit_external_sync EGL_KHR_gl_texture_2D_image EGL_KHR_gl_renderbuffer_image EGL_KHR_create_context EGL_KHR_surfaceless_context EGL_KHR_gl_texture_cubemap_image EGL_EXT_create_context_robustness
Direct rendering	Yes
Reset notification strategy	0x8252
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	Software only
R_16	Software only
RG_88	Software only
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
RGBA_F16	Software only
YVU_420	GPU_READ
YUV_420_BIPLANAR	SCANOUT_CAMERA_READ_WRITE
UYVY_422	Software only
Display(s) Information
Info	Display[0] bounds=0,0 1280x800, workarea=0,0 1280x752, 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
Video Acceleration Information
Encode vp8	up to 1920x1088 pixels and/or 30.000 fps
Encode h264 main	up to 1920x1088 pixels and/or 30.000 fps
Log Messages
[20634:20680:0202/120315.124034:VERBOSE1:drm_device_manager.cc(53)] : Could not initialize DRM device for /sys/devices/platform/vgem/drm/card0
[20634:20680:0202/120316.130253:VERBOSE1:drm_util.cc(379)] : Failed to get EDID blob for connector 43
[20634:20680:0202/120316.165224:VERBOSE1:drm_display.cc(105)] : DRM configuring: device=/sys/devices/platform/display-subsystem/drm/card1 crtc=37 connector=43 origin=0,0 size=1280x800
[20634:20680:0202/120643.387526:VERBOSE1:drm_util.cc(379)] : Failed to get EDID blob for connector 43
[20634:20680:0202/120643.387818:WARNING:screen_manager.cc(114)] : Display controller (crtc=37) already present.
[20634:20680:0202/120643.415197:VERBOSE1:drm_display.cc(105)] : DRM configuring: device=/sys/devices/platform/display-subsystem/drm/card1 crtc=37 connector=43 origin=0,0 size=0x0
[20634:20680:0202/190534.313647:VERBOSE1:drm_util.cc(379)] : Failed to get EDID blob for connector 43
[20634:20680:0202/190534.313875:WARNING:screen_manager.cc(114)] : Display controller (crtc=37) already present.
[20634:20680:0202/190534.342340:VERBOSE1:drm_display.cc(105)] : DRM configuring: device=/sys/devices/platform/display-subsystem/drm/card1 crtc=37 connector=43 origin=0,0 size=1280x800
[20634:20634:0202/195302.301709:ERROR:gles2_cmd_decoder.cc(18162)] : [.DisplayCompositor-0xf5c8c00]GL ERROR :GL_INVALID_OPERATION : glCreateAndConsumeTextureCHROMIUM: invalid mailbox name
[20634:20634:0202/195302.302054:ERROR:gles2_cmd_decoder.cc(10008)] : [.DisplayCompositor-0xf5c8c00]RENDER WARNING: texture bound to texture unit 0 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering.
[20634:20634:0202/195302.302347:ERROR:gles2_cmd_decoder.cc(18162)] : [.DisplayCompositor-0xf5c8c00]GL ERROR :GL_INVALID_OPERATION : glCreateAndConsumeTextureCHROMIUM: invalid mailbox name
[20634:20634:0202/195302.302481:ERROR:gles2_cmd_decoder.cc(10008)] : [.DisplayCompositor-0xf5c8c00]RENDER WARNING: texture bound to texture unit 0 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering.
[20634:20634:0202/195302.302675:ERROR:gles2_cmd_decoder.cc(18162)] : [.DisplayCompositor-0xf5c8c00]GL ERROR :GL_INVALID_OPERATION : glCreateAndConsumeTextureCHROMIUM: invalid mailbox name
[20634:20634:0202/195302.302822:ERROR:gles2_cmd_decoder.cc(10008)] : [.DisplayCompositor-0xf5c8c00]RENDER WARNING: texture bound to texture unit 0 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering.
[20634:20634:0202/195302.303123:ERROR:gles2_cmd_decoder.cc(18162)] : [.DisplayCompositor-0xf5c8c00]GL ERROR :GL_INVALID_OPERATION : glCreateAndConsumeTextureCHROMIUM: invalid mailbox name
[20634:20634:0202/195302.303276:ERROR:gles2_cmd_decoder.cc(10008)] : [.DisplayCompositor-0xf5c8c00]RENDER WARNING: texture bound to texture unit 0 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering.
[20634:20634:0202/195302.303466:ERROR:gles2_cmd_decoder.cc(18162)] : [.DisplayCompositor-0xf5c8c00]GL ERROR :GL_INVALID_OPERATION : glCreateAndConsumeTextureCHROMIUM: invalid mailbox name
[20634:20634:0202/195302.303589:ERROR:gles2_cmd_decoder.cc(10008)] : [.DisplayCompositor-0xf5c8c00]RENDER WARNING: texture bound to texture unit 0 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering.
[20634:20634:0202/195302.303827:ERROR:gles2_cmd_decoder.cc(18162)] : [.DisplayCompositor-0xf5c8c00]GL ERROR :GL_INVALID_OPERATION : glCreateAndConsumeTextureCHROMIUM: invalid mailbox name
[20634:20634:0202/195302.303973:ERROR:gles2_cmd_decoder.cc(10008)] : [.DisplayCompositor-0xf5c8c00]RENDER WARNING: texture bound to texture unit 0 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering.
[20634:20634:0202/195302.304246:ERROR:gles2_cmd_decoder.cc(18162)] : [.DisplayCompositor-0xf5c8c00]GL ERROR :GL_INVALID_OPERATION : glCreateAndConsumeTextureCHROMIUM: invalid mailbox name
[20634:20634:0202/195302.304387:ERROR:gles2_cmd_decoder.cc(10008)] : [.DisplayCompositor-0xf5c8c00]RENDER WARNING: texture bound to texture unit 0 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering.
[20634:20634:0202/195302.304578:ERROR:gles2_cmd_decoder.cc(18162)] : [.DisplayCompositor-0xf5c8c00]GL ERROR :GL_INVALID_OPERATION : glCreateAndConsumeTextureCHROMIUM: invalid mailbox name
[20634:20634:0202/195302.304709:ERROR:gles2_cmd_decoder.cc(10008)] : [.DisplayCompositor-0xf5c8c00]RENDER WARNING: texture bound to texture unit 0 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering.
[20634:20634:0202/195302.304930:ERROR:gles2_cmd_decoder.cc(18162)] : [.DisplayCompositor-0xf5c8c00]GL ERROR :GL_INVALID_OPERATION : glCreateAndConsumeTextureCHROMIUM: invalid mailbox name
[20634:20634:0202/195302.305070:ERROR:gles2_cmd_decoder.cc(10008)] : [.DisplayCompositor-0xf5c8c00]RENDER WARNING: texture bound to texture unit 0 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering.

I have two separate device of the same model, and both shows the problem. They are both manufactured in 2017-10, according to the sticker on the bottomplate.

You can see more infos about the problem in this link. This is where I first troubleshooted: https://productforums.google.com/forum/#!topic/chromebook-central/szSU1ayYQXM;context-place=forum/chromebook-central

There are a few other posts reporting the same bug: 
https://www.youtube.com/watch?v=DsZXZLKH8F4 (same link as the one I posted on "What went wrong?")
https://www.reddit.com/r/chromeos/comments/7ss0zo/chromebook_flickering_on_youtube_anyone_having/
https://productforums.google.com/forum/#!msg/chromebook-central/ineTdFDardE/MsFUVZTWEAAJ
 
A little more background. 

Two other users have reported this issue on the Chromebook Central Help Forum on three other devices. The earliest report was January 15, 2018.

Only appears to impact the Asus C101PA

Issue appears to be related to scaling. From what I can tell it only happens when trying to view a higher resolution video at half the original resolution. The original resolution doesn't matter.

This is not just a YouTube issue. Problem reported to also occur with a downloaded video played using the native Media Player.

Issue appears to only occur on the Chrome OS side. Issue was reported not to occur with Android media players.

Issue reported to occur on stable 63 and beta and dev versions of 64.

Enabling the following flag is reported to correct the problem, but of course also kills overall system performance.

#disable-accelerated-video-decode


Hi,

thanks for the information, that is very helpful.

the factory also reported the same issue to us recently, but they said it's hard to reproduce.


i followed the links, and found Park Sung-Yong's comment at:
https://productforums.google.com/forum/#!topic/chromebook-central/szSU1ayYQXM;context-place=forum/chromebook-central

"Park Sung-Yong said:
I could confirm that it is not an issue of youtube.
https://www.w3schools.com/html/tryit.asp?filename=tryhtml5_video
Since the source video is 320x176, I set the width as 160. The glitch appears when the video plays"

that seems matched the test steps described at #1 right? (half resolution video, no overlay, hardware video decode)

i'll ask the factory to try that to see if we can reproduce this issue easier :)

Comment 3 by a0795a...@gmail.com, Feb 11 2018

Hello,
I am very happy that I've finally got a chance to get it fixed by the right people :)

I am the original poster of your link, Park Sung-Yong, and it is the exact same issue as I posted here. Ask anything you'd like to know, and I'll gladly answer them.

Additionally, I have collected production date from a few people. One person with one glitchy product reported it was manufactured in 2017-09 (https://www.youtube.com/watch?v=DsZXZLKH8F4). I had two products with the issue, and they were both marked as 2017-10, but one person said they had one from 2017-10 without the problem (https://productforums.google.com/d/msg/chromebook-central/szSU1ayYQXM/licFm_G0AwAJ).

Comment 4 by a0795a...@gmail.com, Feb 11 2018

(The production date was on the laptop, not the CPU)
Hi Park Sung-Yong,

thanks, i think this issue might related to the display module or gpu...

if it's possible, could you help to try:
1/ switch to developer mode
2/ enter VT2(or crosh terminal)
3/ run these commands:

localhost # echo '!--enable-hardware-overlays' > /tmp/args
localhost # mount -B /tmp/args /etc/chrome_dev.conf
localhost # restart ui

4/ confirm /etc/chrome_dev.conf has "!--enable-hardware-overlays" at the end of file, then retest this issue

this is to disable our hardware overlays.




i'll open a partner issue to discuss this issue with some googlers and asus team, and update new progress here :)


since the chinese new year is coming, we might be out of office for about 2 weeks.

thanks for your great help again :)

Comment 6 by a0795a...@gmail.com, Feb 11 2018

I will test it probably in 24 hours and tell you the result, but before that, I think I need to tell you this first: I might not be able to do another test, because I have to return it back to the seller soon.

I bought this chromebook on Amazon, and had it shipped to Korea.
Since it is not sold in Korea, it is not likely be covered by Asus Korea -- the operator from the service center said so.

So, to comply with the return policy of Amazon, I have to send it back in a few days.

I will probably order another one, but it should not arrive soon, and it is not certain if the new one will have the same issue or not.
Hi Park Sung-Yong,

it's ok, we can ask the factory to find more problem devices using your test steps:)

but that would be after chinese new year too.


Hi guys,
FYI, the partner issue is:
https://partnerissuetracker.corp.google.com/issues/73189739
so, i've got a feedback from asus, the test steps can repro about 100% on that device.


and disable hardware overlay seems could avoid that

Comment 9 by a0795a...@gmail.com, Feb 12 2018

Thank you for posting the solution!
I haven't tested it yet, but I have a couple of questions

1) Will disabling hardware overlay hinder performance or battery time?
2) What is the likely reason? Hardware defect, device driver error?
(because in the latter case, I won't have to deal with another refund and wait until a patch)

I will test the flag soon and post how it goes.

Happy chinese new year! We, in Korea, also traditionally celebrate it as well :)
Hi Park Sung-Yong,

1/ yes, it could affect that, but not much i think
2/ i'm not sure about that yet, but i think we would fix it in software

and thanks, happy 춘절 too ;)


oh right, I almost forgot posting it
It works seamlessly, much better than just disabling hardware decoding.
I hope it gets patched soon =)
Hi guys,

some updates:
1/ this issue could repro on every bob devices
2/ we found the root cause(wrong hardware register config for yuv hardware overlay), and will upload patches soon :)
CL has been committed and we'll try to get it out in the 65 release of ChromeOS.
Status: Fixed (was: Unconfirmed)
Marking this as fixed, thanks for the bug report.

Sign in to add a comment