New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 862351 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
OOO until 2019-01-24
Closed: Jul 13
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression

Blocking:
issue 862151



Sign in to add a comment

0.2%-0.4% regression in sizes at 573644:573644

Project Member Reported by tdres...@chromium.org, Jul 10

Issue description

See the link to graphs below.
 
All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=862351

(For debugging:) Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?sid=0ac61919240cdbfd92af1e6ad4b062b91d5bcaf3aacf990776b56251226ce4d3


Bot(s) for this bug's original alert(s):

linux
mac
win
win-32
Owner: jiajia....@intel.com
Status: Assigned (was: Untriaged)
Assigning to jiajia.qin@intel.com because this is the only CL in range:
Add webgl2-compute context support in Blink

This change allows web developers to create a 'webgl2-compute' context
which exposes OpenGL ES 3.1 functionality to WebGL.

Bug: 859249
Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel
Change-Id: Ibb403435b18698429e0f1942a15d3e9fa5027fd9
Reviewed-on: https://chromium-review.googlesource.com/1081814
Reviewed-by: Rick Byers <rbyers@chromium.org>
Reviewed-by: Antoine Labour <piman@chromium.org>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Reviewed-by: Kenneth Russell <kbr@chromium.org>
Commit-Queue: Jiajia Qin <jiajia.qin@intel.com>
Cr-Commit-Position: refs/heads/master@{#573644}
Cc: kbr@chromium.org
CC kbr.
Hi ken, Did webgl/webgl2 have the same issue? I suppose the increase of size is normal.
Blocking: 862151
Cc: jiajia....@intel.com
Components: Blink>WebGL
Owner: kbr@chromium.org
Status: WontFix (was: Assigned)
Yes, those APIs had similarly large surfaces and caused similar size increases. For desktop platforms this is not a large problem so I'm closing this as WontFix. However we will continue to investigate this for Android in  Issue 862151 , likely by not compiling in the implementation on that platform.

Sign in to add a comment