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

Issue 604909 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Dec 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug

Blocked on:
issue 365055



Sign in to add a comment

likely memory leak caused by WebGL's gl.bufferData call

Reported by robertm@chromium.org, Apr 19 2016

Issue description


Version: 49.0.2623.112 (Official Build) (64-bit)
OS: Linux 

Load http://art.muth.org/helios.html
Wait 1h-2h
The JS will eventually crash ("out of memory").

Internally the code does essentially:

for each redraw:
   gl.bindBuffer(WEBGL.ELEMENT_ARRAY_BUFFER, buffer);
  [compute new array "data"]
   gl.bufferData(WEBGL.ELEMENT_ARRAY_BUFFER, data, WEBGL.DYNAMIC_DRAW);

So it updates the data for the same buffer over and over again.
GPU memory usage is minimal and does seem to grow.


The code is dart transpiled to JS - so there could be other issues.
However, Firefox does not seem to run out of memory, so Chrome
seems to be the most likely culprit.
Note, that a similar bug was file here for another platform:

https://bugs.chromium.org/p/chromium/issues/detail?id=365055
 

Comment 1 by kbr@chromium.org, Apr 20 2016

Cc: haraken@chromium.org hpayer@chromium.org sigbj...@opera.com
Components: Blink>WebGL Blink>JavaScript Blink>Bindings Blink>MemoryAllocator>GarbageCollection
1-2 hours is quite a long time to reproduce a bug. Can you produce a test case that will reproduce the problem more quickly?

Not sure whether the too-slow collection of these objects is in V8's GC, the bindings, or Oilpan.

Comment 2 by kbr@chromium.org, Apr 20 2016

Labels: Needs-Feedback
Cc: u...@chromium.org
Status: Available (was: Untriaged)
Cc: -sigbj...@opera.com sigbjo...@opera.com

Comment 5 by ajuma@chromium.org, Dec 8 2016

Status: WontFix (was: Available)
Closing given no response to #1.

Sign in to add a comment