New issue
Advanced search Search tips

Issue 890659 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Nov 13
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 2
Type: Compat



Sign in to add a comment

it shows black screen

Reported by sumdr...@gmail.com, Oct 1

Issue description

Example URL:

Steps to reproduce the problem:
1. connect to a web page(ex. m.naver.com)
2. navigate to some page in the domain
3. 

What is the expected behavior?

What went wrong?
it shows black screen but web page work properly such as selecting link, scrolling.

In problem log, it shows below errors.
09-15 06:49:33.249 10210  7721  7754 E chromium: [ERROR:gles2_cmd_decoder.cc(9881)] [.DisplayCompositor-0xc167c400]RENDER WARNING: texture bound to texture unit 0 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering.
09-15 06:49:33.250 10210  7721  7754 E chromium: [ERROR:gles2_cmd_decoder.cc(9881)] [.DisplayCompositor-0xc167c400]RENDER WARNING: texture bound to texture unit 0 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering.
09-15 06:49:33.272 10210  7721  7754 E chromium: [ERROR:gles2_cmd_decoder.cc(9881)] [.DisplayCompositor-0xc167c400]RENDER WARNING: texture bound to texture unit 0 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering.

Does it occur on multiple sites: N/A

Is it a problem with a plugin? N/A 

Did this work before? N/A 

Does this work in other browsers? N/A

Chrome version: 63.0.3239.111  Channel: stable
OS Version: 8.1.0
Flash Version:
 
Components: Internals>Compositing
Labels: Needs-triage-Mobile
Cc: chelamcherla@chromium.org
Labels: Triaged-Mobile Needs-Feedback
sumdra78: Issue is not reproducible on latest stable 69.0.3497.100 using samsung j7 and Pixel. Seems like you are using outdated version of chrome, please check the issue on latest stable and let us know the behavior. If issue is reproducible please provide screencast on reproducing the issue. This would help in further triaging.

Thanks!
Status: WontFix (was: Unconfirmed)
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!

Sign in to add a comment