[Webkit-unassigned] [Bug 177392] WebAssemly + gigacage maxNumWebAssemblyFastMemories = 10 fails
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Fri Sep 22 16:22:56 PDT 2017
https://bugs.webkit.org/show_bug.cgi?id=177392
Filip Pizlo <fpizlo at apple.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |INVALID
--- Comment #1 from Filip Pizlo <fpizlo at apple.com> ---
Not a bug. The purpose of maxNumWebAssemblyFastMemories is to protect us from this case by ensuring the we don’t ever eat up all of the gigacage just with virtual allocations.
--
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/20170922/44fbf6ef/attachment-0001.html>
More information about the webkit-unassigned
mailing list