New issue
Advanced search Search tips

Issue 872999 link

Starred by 3 users
Status: WontFix
Owner: ----
Closed: Aug 17
Cc:
swarnasree.mukkala@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

Worker gets unresponsive with Gpu load and affects heavily pc

Reported by hexerdo...@gmail.com, Aug 10 
UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/68.0.3440.106 Safari/537.36

Steps to reproduce the problem:
1.Navigate https://snipg.github.io/GPUTest/
2.Try it out with chrome 68, as it is without worker. 
3.Now test it with latest Dev or Canarly build.
4.Everything will turn unresponsive

What is the expected behavior?
While doing CPU stress test with worker, everything seems good, and even if you make some bad loop tab just crashes. But when using GPU test, worker can't handle it and pc gets super slow.

What went wrong?
Worker somehow fails to manage GPU load.

Did this work before? N/A 

Chrome version: Version 70.0.3514.0 (Official Build) dev (64-bit),Version 70.0.3517.0 (Official Build) canary (64-bit)  Channel: stable
OS Version: 10.0
Flash Version: 

It Construct 3 GPU test which use worker and  exported as HTML.

Comment 1 by vamshi.kommuri@chromium.org, Aug 10

Labels: Needs-Triage-M70

Comment 2 by swarnasree.mukkala@chromium.org, Aug 10

Cc: swarnasree.mukkala@chromium.org
Labels: Triaged-ET Target-70 M-70 FoundIn-70
Status: Untriaged (was: Unconfirmed)
Able to reproduce the issue on reported version #70.0.3514.0 using Windows 10, by following below steps.
Note: The issue is not observed on Linux(Ubuntu 17.10) and Mac OS(Mac 10.13.6).

Steps:
=====
1.Launched chrome.
2.Opened link https://snipg.github.io/GPUTest, observed that page is unresponsive.

The issue seems to have inconsistent behaviour. Hence marking it as untriaged and requesting dev team to look into the issue and help in further triaging.

Thanks.!

Comment 3 by ajha@chromium.org, Aug 10

Components: Blink>Workers Internals>GPU

Comment 4 by a...@scirra.com, Aug 10 

FWIW the worker uses OffscreenCanvas and the issue does not reproduce with DOM canvas.

Comment 5 by hexerdo...@gmail.com, Aug 13 

After alot of testing i think this is not a bug. Worker or no worker, under hevy GPU load, when requesting it to draw huge amount of sprites it will turn even ordinary chrome 68 super laggy, which is without worker. Or when you move your win 10 calc around desktop it will move with huge spikes, while chrome is under GPU load. But i think this is how it is designed to be.
Why reproduce example link acts differently, depending in worker or no worker is some other issue, and needs  new example and report.

Comment 6 by hexerdo...@gmail.com, Aug 13 

So you guys can close this one.

Comment 7 by bashi@chromium.org, Aug 17

Status: WontFix (was: Untriaged)
Thanks for the follow-up. Let me close this then.
►

Sign in to add a comment