Some WebAssembly programs stress the amount of memory we have available, especially when we consider tiering (BBQ never dies, and is bigger that OMG). Tiering to OMG just piles on more memory, and we're also competing with JavaScript. Separately, I'll try to find places where we allocate too much, and I'll make sure OMG executable allocation failure fails gracefully.
<rdar://problem/32932407>
Created attachment 313659 [details] patch
Comment on attachment 313659 [details] patch Clearing flags on attachment: 313659 Committed r218723: <http://trac.webkit.org/changeset/218723>
All reviewed patches have been landed. Closing bug.
Let's also make it so that we throw an OOM instead of crashing when running out of X memory.
(In reply to Saam Barati from comment #5) > Let's also make it so that we throw an OOM instead of crashing when running > out of X memory. Oh right I don’t know why I thought we’d want otherwise! I’ll do that after my investigation.
(In reply to JF Bastien from comment #6) > (In reply to Saam Barati from comment #5) > > Let's also make it so that we throw an OOM instead of crashing when running > > out of X memory. > > Oh right I don’t know why I thought we’d want otherwise! I’ll do that after > my investigation. That's happening here: https://bugs.webkit.org/show_bug.cgi?id=171537