New issue
Advanced search Search tips

Issue 915255 link

Starred by 2 users
Status: Available
Owner: ----
Cc:
phanindra.mandapaka@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows , Mac
Pri: 2
Type: Bug



Sign in to add a comment

Worker mode - window resize generates more gpu memory and GC won't clean it

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

Steps to reproduce the problem:
1. Open chrome dev(need to be least chrome version 72), navigate https://snipg.github.io/Bugs/WorkerGpu/
2. Open chrome task manager and note GPU memory use
3. Resize window small and back large again with mouse
4. See Least 2x gpu memory use, compared when you opened window first time
5. Use User input double-click to spawn sprites, see GC still won't trigger to clean gpu mem.

What is the expected behavior?
Soon after window resize, Gc to clean gpu memory.

What went wrong?
Gpu memory from window resize won't be cleaned.

Did this work before? N/A 

Does this work in other browsers? N/A

Chrome version: 71.0.3578.98  Channel: stable
OS Version: 10.0
Flash Version: 

See first picture, when browser is opened first time and gpu memory is low.

Secount picture when there has been window resize.
Gpu memory is high.
Kuvatõmmis (139).png
99 KB View Download
Kuvatõmmis (138).png
99 KB View Download

Comment 1 by wanderview@chromium.org, Dec 14

Components: -Blink>ServiceWorker Blink>Workers
AFAICT the service worker is just providing caching and the work is being performed in dedicated workers.

Do you have an example without workers that does cleanup memory as you expect?

Comment 2 by hexerdo...@gmail.com, Dec 14 

Comment 1: yeah
Example without worker: https://snipg.github.io/Bugs/WithoutWorkerGpu/

Without worker GPU use much much slower and always will go back low, pretty fast.

First image, when chrome dev is opened.

Secount image, when chrome dev is opened, resized multipletimes + went fullscreen and back. Results same. So without worker GC does indeal job, while worker does not.

On my laptop i had case. I opened worker example, without resize it had like 80,000k gpu memory, after multiple resizes, it ended up ~360,000k. And it did not go back down!
Kuvatõmmis (140).png
92.7 KB View Download
Kuvatõmmis (141).png
90.7 KB View Download

Comment 3 by phanindra.mandapaka@chromium.org, Dec 15

Labels: Needs-Triage-M71

Comment 4 by phanindra.mandapaka@chromium.org, Dec 21

Cc: phanindra.mandapaka@chromium.org
Labels: Triaged-ET Target-73 M-73 FoundIn-71 FoundIn-72 FoundIn-73 OS-Mac
Status: Untriaged (was: Unconfirmed)
Able to reproduce the issue on reported chrome version 71.0.3578.98 also on latest chrome 73.0.3646.0 using Mac 10.14.0 and Windows 10.  
 
Same behavior is seen on M60(60.0.3112.113) hence considering it as non-regression and marking it as Untriaged.

Note: on Ubuntu 17.10 decreasing the gpu memory while resizing the window.

Thanks..!

Comment 5 by falken@chromium.org, Dec 27

Status: Available (was: Untriaged)
I get the sad tab on my Chromebook when navigating to the demo site with workers, and the one without workers doesn't crash.

Marking available.
►

Sign in to add a comment