[Webkit-unassigned] [Bug 194268] New: Safari does not free ArrayBuffers being transferred from webworker to main thread

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=194268

            Bug ID: 194268
           Summary: Safari does not free ArrayBuffers being transferred
                    from webworker to main thread
           Product: WebKit
           Version: Safari 12
          Hardware: iPhone / iPad
                OS: iOS 12
            Status: NEW
          Severity: Critical
          Priority: P2
         Component: JavaScriptCore
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: hypertree at yahoo.com

Safari frequently runs out of memory running webapps using WebGL libraries such as Mapbox GL-JS and Tangram that transfer large number of araybuffers from webworker to main thread.

This was previously reviewed here and mistakenly marked as RESOLVED/WORKSFORME:
https://bugs.webkit.org/show_bug.cgi?id=172790#c10

Mapbox engineer has provided a small example that clearly shows Safari memory usage growing indefinitely as Safari never garbage collects ArrayBuffrs allocated in the webworker and transferred to foreground thread. Example can be found here (plain simple few lines of JavaScript, no WebGL):
https://measuredweighed.github.io/mapboxgl-js-mem-usage/arraybuffer-test.html

This example also crashes Firefox but rcent version of Chrome is able to garbage collect and keep memory usage down to 1 GB.

Apparently such transfer of arraybuffers is core to WbeGL applications and expected to work.

Safari users of my app have suffered for years and it impossible to release our App for iOS without this issue being fixed.

It seems end is in sight since core issue has been identified.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20190205/ca70fa86/attachment.html>