[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 #8 from Justin Michaud <justin_michaud at apple.com> ---
These data so far seem to show that the memory usage isn't that different between Safari and Chrome, and it is too high in general.

> We got help from v8 engineer who reported compiled wasm size of ~198MB for the wasm (https://readalong.google.com/wasm/wasm/simd/481866636_7/wasm_wrapper_release_simd.wasm) on arm architecture. Is there a way to do the same for webkit?

I am not sure, let me see. Please note though that that is huge. We have a cap at 512MB for performance reasons, see ExecutableAllocator.cpp

In this case though, it seems like GPU memory is the precious resource. I wonder if something is getting leaked, either in your app, the wasm bindings, or inside WebKit.

I can play around with WebInspector later on, but maybe you might be able to get a better idea than me of what is using so much GPU memory on your end.

-- 
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/20230518/716a39b6/attachment-0001.htm>