[Webkit-unassigned] [Bug 256703] [iOS] Wasm based WebApp readalong.google.com reproducibly jetsams

[bugzilla-daemon at webkit.org]

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

--- Comment #20 from tasnim <tasnimrock2k6 at gmail.com> ---
While we are working on reducing memory consumption and especially prioritizing on reducing threads, I wanted to clarify the on-device size of wasmTable. On safari main thread (see screenshot safari_wasm_table), it seems to be taking ~19.56MB whereas on chrome, it takes ~2.1MB (see chrome_wasm_table).

wasmTable seems to be copied over to all web workers. Could this explain why creating threads in safari might be expensive and any optimisation that could be done here?

-- 
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/20230605/cede4b15/attachment-0001.htm>