e.g, checking the allocatedFastMemories integer can be racy. We probably need more fine grained locking around parts of that algorithm.
I think resizing.wast.js runs into that issue. On ARM64 it'll segfault half the time for me.
*** This bug has been marked as a duplicate of bug 170628 ***