I cannot reproduce on a Nexus 5 with Dev (69.0.3457.4) I'm guessing you transposed the version numbers.

Can you provide the exact URI you are loading?

Appeared at least on 27th Jan:
https://productforums.google.com/forum/#!topic/chrome/CrYKrQVVeSw


Personally observed on device hct6735m_35gu_m0

(I observed on YouTube)

I fixed it in my own thanks

How did you fix it ?

Another case, on 69.0.3462:

Huawei y5 lite 2018 / formally known as HUAWEI Y3 2017 (HWCRO-L6737M) - OS Android 6.0

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
Out-of-process Rasterization: Disabled
Hardware Protected Video Decode: Unavailable
Rasterization: Hardware accelerated
Skia Deferred Display List: Disabled
Skia Renderer: Disabled
Surface Synchronization: Disabled
Video Decode: Hardware accelerated
Viz Service Display Compositor: Disabled
WebGL: Hardware accelerated
WebGL2: Hardware accelerated
Driver Bug Workarounds
clear_uniforms_before_first_program_use
disable_framebuffer_cmaa
dont_disable_webgl_when_compositor_context_lost
max_msaa_sample_count_4
max_texture_size_limit_4096
scalarize_vec_and_mat_constructor_args
use_client_side_arrays_for_stream_buffers
use_virtualized_gl_contexts
Problems Detected
Protected video decoding with swap chain is for Windows and Intel only
Disabled Features: protected_video_decode
ARM driver doesn't like uploading lots of buffer data constantly: 178093
Applied Workarounds: use_client_side_arrays_for_stream_buffers
The Mali-Txxx driver does not guarantee flush ordering: 154715, 10068, 269829, 294779, 285292
Applied Workarounds: use_virtualized_gl_contexts
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
Limit max texure size to 4096 on all of Android
Applied Workarounds: max_texture_size_limit_4096
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)
eglSwapBuffers intermittently fails on Android when app goes to background: 744678
Applied Workarounds: dont_disable_webgl_when_compositor_context_lost
Don't expose disjoint_timer_query extensions to WebGL: 808744
Limit MSAA to 4x on Android devices: 797243
Applied Workarounds: max_msaa_sample_count_4
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
Surface synchronization has been disabled by Finch trial or command line.
Disabled Features: surface_synchronization
Viz service display compositor is not enabled by default.
Disabled Features: viz_display_compositor
Skia renderer is not used by default.
Disabled Features: skia_renderer
Skia deferred display list is not used by default.
Disabled Features: skia_deferred_display_list

Deleted: greenscreen2.png 65.2 KB

	greenscreen2.png 65.2 KB View Download

I disabled the "hardware accelerated video decode in chrome flags. Link:chrome://flags/#disable-accelerated-video-decode

Unable to reproduce this issue on Pixel 2(Android 8/9)/ Nexus 5(Android 6)/ Samsung Galaxy J7(Android 7) using 69.0.3547.4, latest stable 69.0.3497.86 and latest canary 71.0.3544.0.

@wongcread1235: Is this issue still seen for you on latest builds? If so could you please provide URLS on which you are seeing this issue.

Thanks!

sorry, missed this one.

from the images, most of them look like an entire frame that's just too small.  my guess is that it's an overlay, and the overlay is being positioned improperly.

however, without a repro, it's going to be very hard to figure out why.

Closing this issue due to lack of feedback from reporter. Please feel free to raise a new issue if this is still seen on latest build #70.0.3538.80.

Thanks!