![]() ![]() These issues already occur when the Wasm page uses only a fraction of total RAM of the device. Here I stress the word reliably, since things may work on some devices for some % of users you deploy to, depending on how much memory your wasm page needs, but as your application's memory needs grow, the % of users you are able to deploy to can dramatically fall. ![]() The short summary is that currently Wasm has grave limitations that make many applications infeasible to be reliably deployed on mobile browsers. After a video call with google last week, I was encouraged to raise a conversation here around issues we at Unity have with Wasm memory allocation.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |