New issue
Advanced search Search tips

Issue 800660 link

Starred by 2 users

Issue metadata

Status: Duplicate
Merged: issue angleproject:2302
Owner: ----
Closed: Jan 2018
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug-Regression



Sign in to add a comment

WebGL performance regression in Chrome 63

Reported by sebastie...@gmail.com, Jan 10 2018

Issue description

UserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.132 Safari/537.36

Steps to reproduce the problem:
1. Open the test case provide on chrome 62
2. Open the test case provide on chrome 63
3. Notice the FPS regression

What is the expected behavior?
FPS should not have regressed

What went wrong?
has regressed

Did this work before? Yes Chrome 62

Does this work in other browsers? N/A

Chrome version: 63.0.3239.132  Channel: stable
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version: 

Data to reproduce have been shared with Kenneth Russel, but are too big to be attached to the bug report
 
Labels: Needs-Bisect Needs-Triage-M63

Comment 2 by kbr@chromium.org, Jan 10 2018

Mergedinto: angleproject:2302
Status: Duplicate (was: Unconfirmed)
Sorry if I wasn't clear but I intended for this to be filed in ANGLE's issue tracker. Moving it there. Please feel free to star that bug or comment.

Sign in to add a comment