Issue metadata
Sign in to add a comment
|
Filling the background with full screen video playback.
Reported by
vzm...@gmail.com,
Apr 15 2017
|
||||||||||||||||||||||
Issue descriptionExample URL: https://kino.pub/ Steps to reproduce the problem: 1. Open https://kino.pub/ 2. Play any video 3. Open the player to full screen What is the expected behavior? When the screen is full screen, the busy video is filled with BLACK. What went wrong? When the screen is full screen, the busy video is filled with WHITE, which is very unpleasant to the eyes. Did this work before? Yes 56 Is it a problem with Flash or HTML5? HTML5 Does this work in other browsers? Yes Chrome version: 57.0.2987.133 Channel: stable OS Version: 6.0.1 Flash Version: - Contents of chrome://gpu: 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: Disabled Native GpuMemoryBuffers: Software only. Hardware acceleration disabled Rasterization: Hardware accelerated Video Decode: Hardware accelerated Video Encode: Software only, hardware acceleration unavailable VPx Video Decode: Hardware accelerated WebGL: Hardware accelerated WebGL2: Unavailable Driver Bug Workarounds clear_uniforms_before_first_program_use disable_chromium_framebuffer_multisample disable_depth_texture disable_framebuffer_cmaa disable_program_cache disable_program_caching_for_transform_feedback disable_timestamp_queries force_cube_map_positive_x_allocation force_update_scissor_state_when_binding_fbo0 max_copy_texture_chromium_size_1048576 max_texture_size_limit_4096 scalarize_vec_and_mat_constructor_args unbind_egl_context_to_flush_driver_caches use_virtualized_gl_contexts wake_up_gpu_before_drawing Problems Detected MediaCodec is still too buggy to use for encoding (b/11536167): 615108 Disabled Features: accelerated_video_encode WebGL 2 is not yet ready on Android: 295792, 641635 Disabled Features: webgl2 Disable depth textures on Android with Qualcomm GPUs Applied Workarounds: disable_depth_texture Non-virtual contexts on Qualcomm sometimes cause out-of-order frames: 289461 Applied Workarounds: use_virtualized_gl_contexts The first draw operation from an idle state is slow: 309734 Applied Workarounds: wake_up_gpu_before_drawing ES3 MSAA is broken on Qualcomm: 449116, 471200, 612474 Applied Workarounds: disable_chromium_framebuffer_multisample 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 EXT_disjoint_timer_query fails after 2 queries on adreno 3xx in lollypop: 477514 Applied Workarounds: disable_timestamp_queries glFinish doesn't clear caches on Android: 509727 Applied Workarounds: unbind_egl_context_to_flush_driver_caches Program binaries contain incorrect bound attribute locations on Adreno 3xx GPUs: 510637 Applied Workarounds: disable_program_cache Android Adreno crashes on binding incomplete cube map texture to FBO: 518889 Applied Workarounds: force_cube_map_positive_x_allocation CHROMIUM_copy_texture with 1MB copy per flush to avoid unwanted cache growth on Adreno: 542478 Applied Workarounds: max_copy_texture_chromium_size_1048576 Limit max texure size to 4096 on all of Android Applied Workarounds: max_texture_size_limit_4096 Limited enabling of Chromium GL_INTEL_framebuffer_CMAA: 535198 Applied Workarounds: disable_framebuffer_cmaa Disable KHR_blend_equation_advanced until cc shaders are updated: 661715 Program binaries don't contain transform feedback varyings on Qualcomm GPUs: 658074 Applied Workarounds: disable_program_caching_for_transform_feedback Certain versions of Qualcomm driver don't setup scissor state correctly when FBO0 is bound.: 670607 Applied Workarounds: force_update_scissor_state_when_binding_fbo0 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 15.04.2017, 11:00:15 Chrome version Chrome/57.0.2987.132 Operating system Android 6.0.1 Software rendering list version 12.13 Driver bug list version 9.29 ANGLE commit id c1a5d16e964a 2D graphics backend Skia/57 ae9cc5d3588d52f4b371b55845704b25d88cf06d Command Line Args --top-controls-show-threshold=0.27 --top-controls-hide-threshold=0.17 --enable-pinch --enable-viewport --enable-overlay-scrollbar --validate-input-event-stream --enable-longpress-drag-selection --touch-selection-strategy=direction --disable-gpu-process-crash-limit --main-frame-resizes-are-orientation-changes --disable-composited-antialiasing --ui-prioritize-in-gpu-process --profiler-timing=0 --prerender-from-omnibox=enabled --enable-dom-distiller --flag-switches-begin --flag-switches-end Driver Information Initialization time 230 In-process GPU false Passthrough Command Decoder false Sandboxed false GPU0 VENDOR = 0x0000 [Qualcomm], DEVICE= 0x0000 [Adreno (TM) 320] Optimus false AMD switchable false Driver vendor Driver version 127.0 Driver date Pixel shader version 3.00 Vertex shader version 3.00 Max. MSAA samples 4 Machine model name Nexus 7 Machine model version GL_VENDOR Qualcomm GL_RENDERER Adreno (TM) 320 GL_VERSION OpenGL ES 3.0 V@127.0 AU@ (GIT@I96aee987eb) GL_EXTENSIONS GL_AMD_compressed_ATC_texture GL_AMD_performance_monitor GL_AMD_program_binary_Z400 GL_EXT_debug_label GL_EXT_debug_marker GL_EXT_discard_framebuffer GL_EXT_robustness GL_EXT_texture_format_BGRA8888 GL_EXT_texture_type_2_10_10_10_REV GL_NV_fence GL_OES_compressed_ETC1_RGB8_texture GL_OES_depth_texture GL_OES_depth24 GL_OES_EGL_image GL_OES_EGL_sync GL_OES_EGL_image_external GL_OES_element_index_uint GL_OES_fbo_render_mipmap GL_OES_fragment_precision_high GL_OES_get_program_binary GL_OES_packed_depth_stencil GL_OES_depth_texture_cube_map GL_OES_rgb8_rgba8 GL_OES_standard_derivatives GL_OES_texture_3D GL_OES_texture_float GL_OES_texture_half_float GL_OES_texture_half_float_linear GL_OES_texture_npot GL_OES_vertex_half_float GL_OES_vertex_type_10_10_10_2 GL_OES_vertex_array_object GL_QCOM_alpha_test GL_QCOM_binning_control GL_QCOM_driver_control GL_QCOM_perfmon_global_mode GL_QCOM_extended_get GL_QCOM_extended_get2 GL_QCOM_tiled_rendering GL_QCOM_writeonly_rendering GL_EXT_sRGB GL_EXT_sRGB_write_control GL_EXT_texture_sRGB_decode GL_EXT_texture_filter_anisotropic GL_EXT_multisampled_render_to_texture GL_EXT_color_buffer_float GL_EXT_color_buffer_half_float GL_EXT_disjoint_timer_query Disabled Extensions GL_KHR_blend_equation_advanced GL_KHR_blend_equation_advanced_coherent GL_OES_depth_texture Window system binding vendor Window system binding version Window system binding extensions 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 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 Video Reproduction Problems https://youtu.be/wOAIbe7TXo0
,
Apr 17 2017
,
Apr 18 2017
Assigning to Frank as I believe he looked into this recently.
,
Apr 18 2017
i can repro locally. it doesn't happen with all sites. haven't figured out what's different with kino.pub yet. in devtools, the gutter is black, even while it's white on the device screen. could be alpha blending issue on the framebuffer. doesn't exactly make sense, though, since HWC shows only the compositor surface -- there's nothing behind the compositor surface. not sure why the image would be different between devtools and device, if not alpha, though. will dig more.
,
Apr 18 2017
turns out that the differens is that kino.pub's content is falling back to MediaPlayer via MediaPlayerRenderer. that, eventually, causes this issue. here's the details: In cases with a white background: - RenderFrameImpl decides to use MediaPlayerRenderer. - RFI does not send a SurfaceManager to WebMediaPlayerImpl - WMPI, when entering full screen, does not have a SurfaceManager, so it can't request a full screen surface (ContentVideoView). - Compositor's layer tree has the default white background (compositor_impl_android.cc sets it) In cases with the black gutter: - RFI sends a SurfaceManager to WMPI - WMPI requests ContentVideoView when entering full screen - The CVV embedder switches the compositor to "has transparent background" mode to support the video underlay. - compositor_impl_android changes the layer tree's background to black. it's going to take some thinking to untangle what's really supposed to be happening. not providing a SurfaceManager is the proper thing to do. it shouldn't have those far-reaching effects.
,
Apr 20 2017
,
Apr 26 2017
Tentatively suggesting 59 as discussed in the b/ bug
,
Apr 26 2017
why RBS? it showed up in 57.
,
Apr 28 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/1423a66d68562cda92de55d3f247ae1c8a155241 commit 1423a66d68562cda92de55d3f247ae1c8a155241 Author: tguilbert <tguilbert@chromium.org> Date: Fri Apr 28 01:54:43 2017 Fix HLS fullscreen gutter color On Android, we currently always tell Blink that we will be using fullscreen overlays. However, the MediaPlayerRenderer does not support them, and does not attempt to use them. The result is that Blink avoids drawing any gutter, which causes the default background color from the LayerTree to be show instead. When no overlay has been created, the default color is white. This CL updates WMPI::SupportsOverlayFullscreenVideo to only return true when we are not using the MediaPlayerRenderer. BUG= 711888 TEST= manually tested on an HLS and non HLS video. Review-Url: https://codereview.chromium.org/2840973002 Cr-Commit-Position: refs/heads/master@{#467821} [modify] https://crrev.com/1423a66d68562cda92de55d3f247ae1c8a155241/media/blink/webmediaplayer_impl.cc
,
May 8 2017
,
May 8 2017
[Auto-generated comment by a script] We noticed that this issue is targeted for M-59; it appears the fix may have landed after branch point, meaning a merge might be required. Please confirm if a merge is required here - if so add Merge-Request-59 label, otherwise remove Merge-TBD label. Thanks.
,
May 8 2017
Omg... Why is that so lOOng, gOOgle?? I already using Yandex browser... even on my job technical support who earn not much money makes things faster, and its google chrome??? Is the chromius some random experimental shit, or millionaires company?! Shame on you!!! If you wont make sense of our troubles, how could you make tools for us to make our life easier?! Moscow is angry on you. Dosviduli. 8 мая 2017 г. 19:16 пользователь "blocker… via monorail" < monorail+v2.383432779@chromium.org> написал:
,
May 8 2017
miguelg: i'm removing RBS since this has been present since 57. talking offline with tguilbert@, the CL above relies on other changes in 60, and can't be merged to 59 safely.
,
May 9 2017
Changing to M60, as per #14.
,
Jun 20 2017
+
,
Jun 20 2017
Samsung Galaxy Tab A
,
Jul 15 2017
++++ Sony Experia Z3 Compat + Z5 Compact. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by vzm...@gmail.com
, Apr 15 2017